From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
Patrick Mochel <mochel@digitalimplant.org>
Subject: [PATCH 2/2] USB: fix up warning messages spit out by the keyspan driver.
Date: Wed, 22 Dec 2004 14:02:13 -0800 [thread overview]
Message-ID: <20041222220213.GB9864@kroah.com> (raw)
In-Reply-To: <20041222220139.GA9864@kroah.com>
I missed this in the previous usb_kill_urb() cleanup. Thanks to
Pat Mochel for reporting this.
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
diff -Nru a/drivers/usb/serial/keyspan.c b/drivers/usb/serial/keyspan.c
--- a/drivers/usb/serial/keyspan.c 2004-12-22 13:42:54 -08:00
+++ b/drivers/usb/serial/keyspan.c 2004-12-22 13:42:54 -08:00
@@ -1121,7 +1121,7 @@
{
if (urb && urb->status == -EINPROGRESS) {
urb->transfer_flags &= ~URB_ASYNC_UNLINK;
- usb_unlink_urb(urb);
+ usb_kill_urb(urb);
}
}
prev parent reply other threads:[~2004-12-22 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 22:01 [PATCH 1/2] USB: drivers/usb/atm/usb_atm.c: fix nonzero snd_padding case Greg KH
2004-12-22 22:02 ` Greg KH [this message]
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=20041222220213.GB9864@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mochel@digitalimplant.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox