From: "William A.(Andy) Adamson" <andros@citi.umich.edu>

this patch fixes the share state sequenceid bookeeping.

- increment the sequence id on an open that is confirmed
- increment the sequence id on close

2.4 kernels are very fussy about some values in the superblock, and
2.6 got them wrong.  This fixes it.

raid1 and multipath have not concept of a chunksize, so basing
max_sectors on it is obviously wrong.

Similary 'linear' has a very different concept of chunksize and
max_sectors doesn't apply.

raid5 does have relevant chunk_size concept, but it has code to
effectively handle any chunksize.

So we only need to set max_sectors based on chunk_size in raid0.

If we get a failure trying to allocate a stripe_head for a read-ahead
request (the only time we can get a failure), we skip the rest of the
request and fail the whole bio.

We don't need to explicitly count references as:
 - refcounting already happens for opens of /dev/md?
 -  when an array is active, a daughter module is loaded which
      locks "md" in.
We just need to make sure we clean up properly on unload. (export_array)

Also, xor needs a null module_exit so that it can be unloaded.

The queue init is really far too verbose at boot time.  I don't think
these messages add anything to either the end user experience or debug
ability. 

Acked by Jens

This assigns the queue properly.

Make everything compile and boot again.

 - Update defconfig
 - Some minor cleanup
 - Introduce physid_t for APIC masks (fixes UP kernels)
 - Add bandaid for CardBus bridges and broken BIOS (Vojtech)
 - Add bandaid for unsynchronized TSCs  (Vojtech)
 - Fix ffs(0) return value (fixes XFS) 
 - Fix compilation with software suspend

synchronize_irq() requires an argument when built with CONFIG_SMP.

As discussed earlier. This implements Linus' idea of printing
the addresses in /proc/<pid>/maps as 32bit if possible.

This works around some broken 32bit programs that cannot parse
64bit addresses as generated by x86-64 kernels.

Also simplifies the code slightly.

CONFIG_ACPI_SLEEP doesn't compile without SOFTWARE_SUSPEND.
Make it select it automagically.

This fixes some bugzilla bug whose number I forgot.

export_ide_init_queue() and export_probe_for_drive()

also fix comment in init_irq()

From Benjamin Herrenschmidt <benh@kernel.crashing.org>.

From Mikael Pettersson <mikpe@csd.uu.se>.

From Stephane Ouellette <ouellettes@videotron.ca>.

From Mikael Pettersson <mikpe@csd.uu.se>.

From Duncan Laurie <duncan@sun.com>

This same patch made its way into 2.4 via the -ac tree but hasn't
been put in 2.6 yet.

It fixes some cable detect issues that stem from the fact that the
cable detect pins are also used as address/data lines, so they need
to first be configured as inputs to read valid cable detect state.

One more overlooked area where the proper process ID has to be used:
SysV IPC "pid" values should use the thread group ID, not the per-thread
one.

sound/pcmcia/vx/vx_entry.c:

This patch removes the PCMCIA timer release functionality which is no
longer required. Without this the module does not compile.

Too much cut-and-paste, noticed by Dmitry Torokhov <dtor_core@ameritech.net>

into samba.org:/home/paulus/kernel/for-linus-ppc

On PPC32 we reorder the arguments so they fit into 6 registers.  Glibc will
need a two-line stub to change them from the standard order to the ordering
used by the system call: (fd, advice, offset, len).

into samba.org:/home/paulus/kernel/for-linus-ppc

into samba.org:/stuff/paulus/kernel/for-linus-ppc

into samba.org:/stuff/paulus/kernel/for-linus-ppc

into samba.org:/stuff/paulus/kernel/for-linus-ppc

into samba.org:/stuff/paulus/kernel/for-linus-ppc

In both 2.4 and in 2.6, error handling for bad cdrom media is
wrong.  And it is my fault I'm afraid, since I botched an earlier
fix for the problem by putting the fix in the wrong spot.

My kids have a "Jumpstart Toddlers" cd they have long since
completely killed, which makes a great test disc.  Without this
fix, the best time projection I can get for completing a dd type
sector copy is about 2 years...  Most of that is spent thrashing
about in kernel space trying to re-read sectors we already know
are not correctable....  After the fix, I was able to rip a copy
the CD (or rather muddle through it getting lots of EIO errors)
in about 15 minutes.

Attached is the fix for 2.6.x,