All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Greg KH <gregkh@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-usb@vger.kernel.org
Subject: Re: libusb broken on 2.6.28 x86_64 ?
Date: Fri, 02 Jan 2009 04:37:36 -0500	[thread overview]
Message-ID: <495DE060.8040707@rtr.ca> (raw)
In-Reply-To: <20090102082824.GA4212@suse.de>

Greg KH wrote:
..
> Hm, care to run 'git bisect'?
..

No, thanks.  But the number of USB core changes in 2.6.28 is rather small,
so I just ended up looking at each of them in more detail.

This patch, below, FIXES it for me, by undoing a change from 2.6.28.

Signed-off-by: Mark Lord <mlord@pobox.com>

--- old/drivers/usb/core/driver.c	2008-12-24 18:26:37.000000000 -0500
+++ linux/drivers/usb/core/driver.c	2009-01-02 04:34:11.000000000 -0500
@@ -279,9 +279,7 @@
 	 * altsetting means creating new endpoint device entries).
 	 * When either of these happens, defer the Set-Interface.
 	 */
-	if (intf->cur_altsetting->desc.bAlternateSetting == 0)
-		;	/* Already in altsetting 0 so skip Set-Interface */
-	else if (!error && intf->dev.power.status == DPM_ON)
+	if (!error && intf->dev.power.status == DPM_ON)
 		usb_set_interface(udev, intf->altsetting[0].
 				desc.bInterfaceNumber, 0);
 	else

  reply	other threads:[~2009-01-02  9:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  6:31 libusb broken on 2.6.28 x86_64 ? Mark Lord
2009-01-02  7:01 ` Mark Lord
2009-01-02  7:24   ` Greg KH
2009-01-02  7:48     ` Mark Lord
2009-01-02  7:51     ` Mark Lord
2009-01-02  7:58       ` Greg KH
2009-01-02  8:15         ` Mark Lord
2009-01-02  8:25           ` Mark Lord
2009-01-02  8:28           ` Greg KH
2009-01-02  9:37             ` Mark Lord [this message]
2009-01-02 13:23               ` Alan Stern
2009-01-02 15:44                 ` Mark Lord
     [not found] <20090102082824.GA4212@suse.de.suse.lists.linux.kernel>
2009-01-02 11:43 ` Marcus Meissner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=495DE060.8040707@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.