There is still more work to do, the driver sucks in 2.4 and 2.5 but 2.5 has a
lot more of what is needed to make it work nicely. Basically NCR5380_main
probably has to become a thread in the next generation of the code.

This however seems to get it up and crawling

(From Matthew Wilcox)

(Jaroslav you may want to clone this into ALSA if ALSA lacks this one)

After reverting my nice but totally broken idea about accelerating
the linking steps, make the three-stage .tmp_kallsyms.o generation
/ addition work again.

Yeah, that means that we now link vmlinux three times when
CONFIG_KALLSYMS is set, and that's annoying.

into mulgrave.(none):/home/jejb/BK/scsi-for-linus-2.5

into mulgrave.(none):/home/jejb/BK/scsi-for-linus-2.5

That's the last one.  Now we can start doing refcounting...

smbfs compilation fix

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

We removed some files which are long since dead, but on the other
hand forgot some of the current ones.

Also, add a missing ) in a warning (introduced and fixed by Sam Ravnborg ;)

If you hide the sub-make in a function, 'make' needs a little help...

In addition to usual switch and cleanup, switched the damn thing
to use of module_init/module_exit (and removed call from device_init()).

That also matches the other dependency filenames these days,
and makes the tree more position-independent.

Missed memset() when switching DAC960 to alloc_disk().  Fixed.

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

The kallsyms patches added __kallsyms as last section into vmlinux,
behind .bss.

This was done to save two additional kallsyms passes, since as the
added section was last, it did not change the symbols before it.

With the new infrastructure in the top-level Makefile, we do not need
to do full relinks for these passes, so they are cheaper. We now
use one additional link/kallsyms run to be able to place the __kallsyms
section before .bss. The other pass is saved by adding an empty but 
allocated __kallsyms section in kernel/kallsyms.c, so the first kallsyms
pass already generates a section of the final size.

kallsyms needs to actually have a final vmlinux to extract the symbols,
and then add this information as a new section to the final vmlinux.

Currently, we basically just do the vmlinux link twice, adding
.tmp_kallsyms.o the second time. However, it's actually possible to just
link together the temporary vmlinux generated the first time and the
new object file directly without going back to all the single parts
that the temporary vmlinux was linked from.

This mechanism should be useful for sparc as well, where the btfix
mechanism needs an already linked vmlinux, too.

IMPORTANT: This does only work as desired if the link script can be
used recursively, i.e.

ld <flags> -T arch/$(ARCH)/vmlinux.lds.s -o vmlinux.test vmlinux

generates a vmlinux.test which is identical to vmlinux.
arch/i386/vmlinux.lds.S needed a little tweaking, so probably the
other archs do as well.

This patch removes the stubs for syscalls that are not used from the
kernel anymore.