[patch 1/3]Re: respin of patches to usb-skeleton

Oliver Neukum <[email protected]>
Newsgroups gmane.linux.usb.devel
Organization Novell
Message-ID <[email protected]>
Am Freitag, 8. Juni 2007 schrieb Greg KH:
> On Sun, Jun 03, 2007 at 12:31:34PM +0200, Oliver Neukum wrote:
> > Hi Greg,
> > 
> > I've redone them against 2.6.22-rc3 and they are identical.
> > Kernel.org hiwever has no patch set of yours against rc3. Which
> > tree should I rediff against.
> 
> Hm, can you grab my quilt tree from kernel.org and apply them against
> the end of that:
> 	http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-03-usb/
> 
> > PS: This took some time because my laptop's power brick was stolen
> > at Linuxtag.
> 
> That really sucks :(

Moreover, it doesn't make sense. Now I have a universal power brick which
would be actually useful to a thief.

Here it is against your tree. It conflicted with Alan's disconnect/open fix.

1/3: use anchors in disconnect handling

	Regards
		Oliver
Signed-off-by: Oliver Neukum <[email protected]>
--

--- linux-2.6.22-rc4-git2/drivers/usb/usb-skeleton.c.alt	2007-06-11 13:31:36.000000000 +0200
+++ linux-2.6.22-rc4-git2/drivers/usb/usb-skeleton.c	2007-06-11 13:45:17.000000000 +0200
@@ -420,6 +420,8 @@ static void skel_disconnect(struct usb_i
 	dev->interface = NULL;
 	mutex_unlock(&dev->io_mutex);
 
+	usb_kill_anchored_urbs(&dev->submitted);
+
 	/* decrement our usage count */
 	kref_put(&dev->kref, skel_delete);
 

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.