Group related things together, like building vmlinux,
building modules, generating dependency, configuration, etc.

Nobody is building files from the top-level Makefile anyway, and
if they were, they should use the standard assembler rules 
provided by Rules.make

The targets {sgml,ps,pdf,html} docs work as before, but
the handling is now completely in Documentation/DocBook/Makefile.

The ROOT_DEV, SVGA_MODE and RAMDISK variables are i386/x86_64
specific, so move them to arch/$(ARCH)/boot/Makefile, this
is where they are used.

They still can be overridden on the command line like before,
though I doubt anybody is still using them.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

Adding some more flexibility to Config.in (Allow for core built-in but
socket driver modular) cleans up the Makefile as well ;-)

Use the usual list-based approach. Still not too nice.

Old pcmcia-cs versions expect the pcmcia modules in 
/lib/modules/`uname -r`/pcmcia, so we symlinked them for compatibility.
According to the comment, the generation of these links should have
been removed in 2.4, so it's definitely time for it to go now.

Don't shortcut from drivers/Makefile to 
drivers/message/{fusion,i2o}/Makefile, but use intermediate
drivers/message/Makefile.

Cleanup drivers/message/fusion/Config.in and get rid of unnecessary
CONFIG_FUSION_BOOT.

Link the subdirs of drivers/char from drivers/char/Makefile instead the
top-level Makefile. 

Link order changes slightly, shouldn't case any problems, though.

Fix drivers/char/pcmcia/Config.in.

Cleanup drivers/char/pcmcia/Makefile.

Fix rio build rules in drivers/char/Makefile.

into home.transmeta.com:/home/torvalds/v2.5/linux

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make

into home.transmeta.com:/home/torvalds/v2.5/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

There's actually two cases when a new NCCI is created:
outgoing and incoming connections (had missed the latter)

above explaining the {phys,pfn}_base stuff.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

Applications really ought to take care of maintaing the state themselves,
instead of cheating by listening to controller private messages.

    - Report better errors, and in one case the correct one.
    - Adds strategic wmb() calls
    - Claims the right (scaled) ISO bandwidth
    - Uses non-CVS version ID

This will likely resolve that Archos MP3 Jukebox issue, where "-104"
(-ECONNRESET) was appearing mysteriously.

minor -dj tree updates.

add PMAC changes found in -dj tree

sync up with -dj tree

First step in having the users alloc this as part of the state info
they have to maintain anyway.

change due to moved location of i386's pci.h

    - generalizes/cleans keventd support to also handle
        * rx stalls (and usb 2.0 transaction translator unplug)
        * rx memory shortfalls (latent bug Oliver noticed)
        * cleanup on device disconnect (quiesce first)
    - merges Brad's patch to use the IEEE802 "locally assigned" bit
    - fixes a couple minor bugs on error paths (leak, bogus diagnostic)
    - updates some comments

into home.transmeta.com:/home/torvalds/v2.5/linux

Ah.  That's some left-over code.  Reads will be OK, but writes will be
unexpectedly asynchronous.  Nothing in the kernel uses that function for
writes so it didn't show up.

  Trivial patch to change some instances of suser() and fsuser() to
proper capable() checks.

In Rules.make, a comment says:

# Old makefiles define their own rules for compiling .S files,
# but these standard rules are available for any Makefile that
# wants to use them.  Our plan is to incrementally convert all
# the Makefiles to these standard rules.  -- rmk, mec

This patch does that for the i386 arch Makefiles.