I overlooked that setting control lines in open can fail.

  - check for error doing control transfers
Signed-Off-By: Oliver Neukum <oliver@neukum.name>
Signed-off-by: Vojtech Pavlik <vojtech@suse.cz>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

  - races with urb->current, union header evaluation, DMA handling
Signed-off-By: Oliver Neukum <oliver@neukum.name>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch fixes another bug in the dummy_hcd driver.  When a gadget
driver unregisters (simulating a device disconnect), dummy_hcd stops the
timer that it uses for processing outstanding URBs.  Unfortunately this
means that those URBs will never be given back.  The patch lets the timer
continue running; when it expires all the remaining URBs will fail so the
timer won't be reinitialized.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch implements the missing functionality necessary to get device
resets working fully.  It adds a bit-array of ports with logical
connect-changes pending to the hub structure, so that the hub driver can
recognize that these ports should be treated as though they had
disconnected and re-connected.  This is how we will handle devices that
"morph" (i.e., change their descriptors) following a reset, as might
happen with a firmware upload.

There is also a lot of additional kerneldoc and a few small changes to
some log messages.  An important restriction is that usb_reset_device()
will refuse to work if the device is suspended.  Trying to reset a
suspended device leads to several problems, not least of which is that the
device's parent hub might be suspended as well.

With this patch the device reset code is pretty much complete.  However it
won't always work correctly until the device locking is straightened out.
That's coming up next.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

Also clean it all up - use get_cpu()/put_cpu() instead of
playing games by hand with preemption.

Here is a simple patch which drops some out-of-date code in the w83781d
and w83627hf i2c chip drivers. These bits are left over from the times
when chip drivers were setting default limits at init.


Signed-off-by: Jean Delvare <khali at linux-fr dot org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

into kroah.com:/home/greg/linux/BK/driver-2.6

Al missed this one in his sparse fixes
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

From: Mika Kukkonen <mika@osdl.org>
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

From: Mika Kukkonen <mika@osdl.org>
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

From: Mika Kukkonen <mika@osdl.org>
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Split ata_eng_timeout into the main part (ata_qc_timeout)
and the part called by the SCSI layer (ata_eng_timeout).

Zero behavior changes.

On Sun, Jun 20, 2004 at 05:46:32PM -0700, Andrew Morton wrote:
>...
> All 226 patches:
>...
> bk-libata.patch
>...

drivers/scsi/hosts.h is obsolete, use scsi/scsi_host.h.

Please apply
Adrian

by "other". The normal permissions for the kernel tree
should be -rw-r--r--.

sock_fprog instances that had kernel pointer in ->filter (both of them -
in ppp_generic and isdn_ppp) replaced with explicit pairs len + kernel
pointer.  Copying of userland sock_fprog (with its __user ->filter)
cleaned up and sanitized.

Trivial annotation done in the rest of ->ioctl() in ppp_generic and
isdn_ppp.

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into intel.com:/home/lenb/bk/linux-acpi-test-2.6.7

Reflect that only the dstirq depends on the dstapic.

into intel.com:/home/lenb/bk/linux-acpi-test-2.6.7

caused by errant fix for OSDL 2835

Requested by Promise.  The hardware isn't widely deployed yet,
with almost all users being early evaluators, so this should be OK.