patch fixes it: alt-arrow has to start from console _we want to switch
to_, if switch is already pending.

       Added Logitech MOMO FF steering wheel ID.

       init order to make some of the probing code (second irq probe)
       unnecessary.

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

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

Thanks to DaveM.

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

Obviously almost noone uses the pdeath_signal feature, since this has gone
unnoticed for quite some time.

This patch calls the function that does the right locking for the context
of this call (inside exit_notify).  The names of the signal.c entrypoints
are a little confusing.

The spinlock was held while calling functions that could block,
while simultaneously being at all times inside the context of
module init/exit.

Thanks to DaveM.

	correctly even on 32-bit hosts. As an added bonus, it's faster,
	too.  Run "unwcheck" by default, but for now, don't let unwcheck
	errors cause the kernel build to fail.

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

This patch fixes DMA bugs on x86-64 and ia64 machines.  The driver was
using commands that only support 32bit addresses in places that could
return 64bit addresses.  One place was DMAing off the stack.  The other
place was causing problems on x86-64 machines by calling pci_map()
functions on a region allocated by pci_alloc_consistent().

This patch fixes two minor bugs.  It allows zero length write commands
through to devices.  It also prevents the writing of any  '\0'
characters at the end of version numbers to ips's /proc/scsi files.

From: "Andrew Vasquez" <andrew.vasquez@qlogic.com>

With additional changes from: "James Bottomley" <James.Bottomley@SteelEye.com>,
                              "Christoph Hellwig" <hch@infradead.org>

This is the qlogic driver version 8.00.00b7 with the ioctl and failover code stripped
out and a few associated fixes put in.

From: "Randy.Dunlap" <rddunlap@osdl.org>

The problem is that the detect function requests an IO region
of 16 bytes (at least when a command line override parameter is
used) but the release function only tries to release 8 bytes,
and this request isn't done because it doesn't match any allocated
IO region.  [NCR53C400 extensions are not enabled, so
NCR5380_region_size is 8, not 16, but the request uses
NCR5380_region_size regardless.]

Fix: save the allocated region size in instance->n_io_ports and release
   that size only;

       the load on the controller (only one status read per interrupt). Also
       do polling only some time after an interrupt happened.

       compatibility as we can at the moment. This also kills
       KEY_103RD, because PS/2 keyboards don't have it and
       everyone is expecting to get KEY_BACKSLASH anyway. Fix
       rawmode generation for PrintScreen key, too.

Fixes build on some platforms.

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

  This was broken by the last commit for cdev stuff which removed the
  "int ret;" that these routines used.