hex component of an error message only comes out when the
message does.

SGI Modid: 2.5.x-xfs:slinx:153268a

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

into kernel.bkbits.net:/home/davem/sparc-2.5

This uses CLONE_KERNEL in place of the individual
flags, only changing the places where it is an exact
match.

I strongly suspect that CLONE_KERNEL ought to be
used in many more places, but they require a more
careful examination.

link-time duplicate symbol errors.

into kernel.bkbits.net:/home/davem/net-2.5

into nuts.ninka.net:/disk1/davem/BK/net-2.5

Now all is in llc2.ko, so no need for exporting those symbols.
Also llc_build_and_send_ui_pkt is now in llc_output.c, where it
is being exported.

into nuts.ninka.net:/disk1/davem/BK/net-2.5

into nuts.ninka.net:/disk1/davem/BK/net-2.5

into home.osdl.org:/home/torvalds/v2.5/linux

This patch moves some unnecessary global functions to the local
pnpbios include file.

It looks like this option has been moved from isapnp to resource.c,
but the MODULE_PARM line is still there:

patch from: Gerald Teschl <gt@esi.ac.at>

From: Randy Hron <rwhron@earthlink.net>

The original argument for blocking DMA 0 was to avoid conflicts with
"memory refresh"  but such configurations are only found on very old
8-bit systems that are likely not supported by the linux kernel. 
This patch allows dma 0 to be assigned to PnP devices by default.  If
for whatever reason dma 0 cannot be used, one can avoid allocating it
by setting the pnp_reserve_dma= kernel parameter.

This patch moves the detection code to a more appropriate file.

When a driver's probe routine fails, it may not release all of the
card devices it requested.  This patch allows the pnp layer to ensure
that all devices claimed by the failing driver are released properly.

Here's an updated patch that will correct the compile error when PROC
FS is disabled.  It also introduces better proc error recovery and
moves the local proc functions to the local include file.  Thanks to
Daniele Bellucci for finding the problem and contributing to this
patch.

This fixes the thread-aware /proc for CONFIG_SECURE.

bad_flp_intr() in floppy.c can cause an Oops if the I/O request is freed
but <errors> still points into the I/O request block.  Get the error
count out of the request block before ending the IO.

bad_flp_intr() oopsen reports:

  Andrey: http://marc.theaimsgroup.com/?l=linux-kernel&m=105837886921297&w=2
  John:   http://marc.theaimsgroup.com/?l=linux-kernel&m=106303650007125&w=2
  Barry:  http://bugme.osdl.org/show_bug.cgi?id=1033

From: Felipe W Damasio <felipewd@terra.com.br>

Fix a few error-path leaks in the cciss block driver.  Bug found by smatch
checker.

make_pages_present() can fail: propagate that failure back.

Spotted by Bill Irwin.

From: Adrian Bunk <bunk@fs.tum.de>

Three drivers under drivers/char/ in 2.5.72 use TWO_ZERO for compatibility
code with ancient 2.0 kernels.  The patch below removes this #ifdef'd code.

From: Christoph Hellwig <hch@lst.de>

keeping init order the same..

From: Christoph Hellwig <hch@lst.de>

now that kdev_t is gone very few places needs this still, the only header
of those beeing fs.h

From: Nick Piggin <piggin@cyberone.com.au>

If a request is merged with another, it sometimes has to be repositioned on
the rbtree - you just do a delete then an add.  This is a quite uncommon
case though.

I changed the way adding works, so collisions must be handled by the caller
instead of being dumbly fixed by the add routine.  Unfortunately the
uncommon callers weren't handling it properly.