into kroah.com:/home/greg/linux/BK/gregkh-2.5

- some access to urb->hcpriv and urb->status needed to be
   locked using urb->lock
- paranoia: don't depend on two values being in lock-step.

into kroah.com:/home/linux/linux/BK/gregkh-2.5

This patch converts most common hub diagnostics to use the
device model diagnostic macros ... not all, someone should
reduce the number of err() strings for "bogus hub" cases,
and ideally streamline some of the dozen or so "here's what's
special about this new hub" dbg() messages.

So the messages become more useful:  they id the port (and
implicitly the device) involved, using a kernel-wide standard
convention.  Size overhead is smaller too.

For folk running with USB debugging enabled, it also cuts
the useless chatter on connections by deleting the per-poll
success messages and a partial dup message when things change.
And it deletes a newish diagnostic on a (non-hub) unlink path.

It also makes Pete's new debounce message use the right
port number -- one-based, not zero-based.

My main issue with this patch is that it doesn't change
more messages, but it seems reasonable to merge it anyway.

unknown ioctls return -ENOTTY and nothing else.

checking for -EINPROGRESS is wrong.

this makes sure that the kernel thread is dead and gone on module unload.
  - use a completion to wait for the kernel thread's death

Don't try to dereference the interrupt endpoint if it doesn't exist.

2.5.50 included a change from -ac which changed MSNDCLAS_HAVE_BOOT and
MSNDPIN_HAVE_BOOT to asked questions. This is wrong (I know since I was
the one who wrote the patch Alan picked up...).

They shouldn't ask questions, the following patch reverts my buggy
change.

The change to eata_pio_proc.c contained a typo: a semicolon instead of a
comma.

elf AUX-table entry.

Move the 'vsyscall' page to 0xffffe000, leaving a hole at the top
of the address space.

Older gcc's do not support that form of ellipsis in a macro.

Instead of doing a "int 0x80" instruction for system calls,
user space can do a "call 0xfffff000" which will do the right
thing regardless of what kind of system call support the CPU
has.

This cleans up the bus/usb-serial/drivers/ directory

This patch fixes interpret_urb_result in two major ways:
(1) Uses a switch() instead of nested if() statements
(2) Handle -EREMOTEIO to indicate a short scatter-gather transfer

Well, two patches in one... These patches will bring the PWC (Philips
Webcam) driver in both 2.4.20 and 2.5.51 up to version 8.10. Functionally,
the two branches are the same (about 70% of the code is shared), but the
differences in kernel architecture are too large to handle with a few
#ifdefs.

This patch fixes the following (this are only the differences between 8.9
and 8.10):

* Fixed ID for QuickCam Notebook pro
* Added GREALSIZE ioctl() call
* Fixed bug in case PWCX was not loaded and invalid size was set

This patch against 2.5.51 removes the remaining typedefs from usbvideo

typedef enum { .. } ScanState_t -> enum ScanState
typedef enum { .. } ParseState_t -> enum ParseState
typedef enum { .. } FrameState_t -> enum FrameState
typedef enum { .. } Deinterlace_t -> enum Deinterlace
typedef struct { .. } usbvideo_t -> struct usbvideo

small fixes flushed by the hunt for bigger game:

- terminate td lists with dummy, not list end marker
- use alt_next only for real short control reads
- un-halt async qhs before scheduling
- deletes unused debug code, pointless assignments
- surely nobody ever sees that memleak
- terminate two related "while" loops the same way

This patch:

- Removes Pavel's Zaurus-private crc32 code; the base patch
   was from Pavel.

- Addresses two issues Toby Milne reported against the Zaurus:
   (a) if skbs had extra framing added (z, net1080, gl620a),
       the original size (now too small) was used on tx;
   (b) added FLAG_FRAMING_Z so rx packets had enough space

- Removes an oops from the driver model conversion (saved
   the wrong pointer).  Disconnecting wasn't healthy.

- Forward-ports some ethtool support from the 2.4 version:
   PDAs are always connected, so report them that way.

- Stubs in some PXA-250 support for non-Zaurus PDAs.
   This is currently commented out; so far those PDAs
   only run Linux for bleeding edge developers.

- Minor cleanups.

This is the rest of the work to remove the tasklet: the non-syntax
portions which affect work scheduling.  It's not quite davem's version;
it's got locking updates, which among other things prevent a hang when
the timer kicks in.

This scheduling change is split out from the other parts in case more
problems like that unlink race (fixed in my previous patch) show up.
It doesn't fix (or help fix) any ehci bugs, but simpler code is fine.

This should be innocuous; I expect most folk won't notice anything
better (or worse) from this patch unless they're using Intel EHCI.

removing tasklet
     - parts of davem's patch (passing pt_regs down)
     - remove 'max_completions'
     - update cleanup after hc died
     - fix an urb unlink oops (null ptr) that happens more often this way

talking to hardware
     - fixes for some short read issues (may still be others)
	* use qtd->hw_alt_next to stop qh processing after short reads
	* detect/report short reads differently
     - longer reset timeout (it was excessively short, broke Intel)

other
     - simpler diagnostics portability to 2.4:  wrap dev_err() etc
     - urb unlink wait and non-wait unlink codepaths share most code
     - don't try ehci_stop() in interrupt context (bug from hcd layer)
     - minor stuff, including
	* some "after hc died" paths were wrong
	* verbose debug messages compile again
	* don't break error irq count

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

The linear target was getting the start sector wrong when doing a
dm_get_device(). [Kevin Corry]

The block layer does not honour bio->bi_size when issuing io, instead
it performs io to the complete bvecs.  This means we have to change
the bio splitting code slightly.

Given a bio we repeatedly apply one of the following three operations
until there is no more io left in the bio:

1) The remaining io does not cross an io/target boundary, so just
   create a clone and issue all of the io.

2) There are some bvecs at the start of the bio that are not split by
   a target boundary.  Create a clone for these bvecs only.

3) The first bvec needs splitting, use bio_alloc() to create *two*
   bios, one for the first half of the bvec, the other for the second
   half.  A bvec can never contain more than one boundary.

o  If there's an error you still need to call bio_endio with bio->bi_size
   as the 'done' param.

o  Simplify clone_endio.

[Kevin Corry]

Remove verbose debug message 'Splitting page'.

Remove some paranoia in highmem.c

Some fields in the duplicated bio weren't being set up properly in
__split_page(). [Kevin Corry]

md->pending was being incremented for each clone rather than just
once. [Kevin Corry]

dec_pending(): only bother spin locking if io->error is going to be
updated. [Kevin Corry]

Add a blk_run_queues() call to encourage pending io to flush
when we're doing a dm_suspend().

dm_suspend(): Stop holding the read lock around the while loop that
waits for pending io to complete.

queue_io() was checking the DMF_SUSPENDED flag rather than the new
DMF_BLOCK_IO flag.  This meant suspend could deadlock under load.

Give each device its own io mempool to avoid a potential
deadlock with stacked devices.  [HM + EJT]