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

We now always allocate the section __ksymtab, which to modutils means
not to implicitly export any symbols.

That means that EXPORT_NO_SYMBOLS is now default, and thus can go away
in the sources.

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

o Standardize building math-emu.o for arch/alpha
o Remove old boilerplate code / redundant comments
o Remove unnecessary obj-m := $(sort $(obj-m)) in ALSA

o Use a shorter expression to transform 'foo.o' -> 'foo-objs'
o Define EXPORT_FLAGS (as -DEXPORT_SYMTAB) in the main Makefile
o Small rearrangement of code in Rules.make

The attached patch fixes the compilation problems Andrew Morton has been
seeing with the rw-semaphores in the kernel when using gcc 2.95.3 with
-O1.

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

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

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

(Christoph Hellwig)

The copy_to/from_user fixes left some variables unused, which
the compiler warned about.

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

- Yes we really do need sched.h in central.c
- Include namei.h in solaris syscall emul layer
- Use generic_fls in sparc64 bitops.
- Add dummy asm-sparc64/suspend.h

- Include dcache.h/namei.h in fs/autofs/autofs_i.h not dirhash.c
- Include list.h and spinlock.h in dcache.h
- Include list.h in mount.h and namei.h

Removed lots of unneeded #includes from the tty style drivers.

addition of #include <linux/version.h> due to removal from <linux/usb.h>

fix compile time error, due to addition of jiffies.h

Group the variable-processing part together, which figures out what
needs to be done. (Nothing actually changes in this cset)

We have
o CFLAGS_KERNEL: Additional flags for files compiled into vmlinux
o AFLAGS_KERNEL: Additional flags for files assembled into vmlinux
o MODFLAGS: Additonal flags for files compiled as module

For consistency, rename MODFLAGS to CFLAGS_MODULE, introduce
AFLAGS_MODULE but leave it empty for now.

While we're at, removing "MAKING_MODULES=1", nobody is using it.

Here is an updated patch for the floppy driver which got broken in
2.5.13. "read block 0 on ->revalidate()" is now implemented through
the bio interface, following a suggestion by Christoph Hellwig.

I still cannot explain why block_dev.c's ->bd_block_size change
caused data corruption, but removing that code fixes the floppy
driver and doesn't seem to cause any problems on my test box.

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

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

If our command line contains an ';', we'd only print half of
it and execute the other half - not good.

This patch removes the quicklist support and updates m68k to the recent
page table and tlb interface changes.
It also includes some smaller cleanups:
- turn "extern inline" into "static inline"
- convert some macros into inline functions

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

Removed the use of the next field due to the change in the urb structure.

Removed the use of the next field due to the change in the urb structure.

Use the just introduced Rules.make extension to clean up 
drivers/net/*/Makefile.

New-style Makefiles have a nice way of declaring objects
which need to be built either built-in or as modules:

        obj-$(CONFIG_EEPRO100) += eepro100.o

However, handling objects in subdirectories, which need to be
built and linked is not as nice:

        subdir-$(CONFIG_E100) += e100

        ifeq ($(CONFIG_E100),y)
          obj-y += e100/built-in.o
        endif

This means we descend into the subdirectory when building
vmlinux / modules, depending on CONFIG_XXX. When we are building
vmlinux we also need to link whatever has been built in the
subdirectory, so we add it to $(obj-y) at the appropriate place
(link order is important).

Now, the extension below allows to rewrite the second case into

         obj-$(CONFIG_E100) += e100/

which looks much nicer ;-) Existing behavior is not changed, and the
only prerequisite to using the extension above is that the O_TARGET in
the subdir is named "built-in.o".