From: Dmitry Torokhov <dtor@insightbb.com>
To: johann deneux <johann.deneux@gmail.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH] iforce: Use usb_kill_urb instead of usb_unlink_urb.
Date: Sat, 17 Mar 2007 21:37:22 -0400 [thread overview]
Message-ID: <200703172137.23385.dtor@insightbb.com> (raw)
In-Reply-To: <38b3b7c0703171450q5217f4eer91e7ba0f6135d98@mail.gmail.com>
Hi Johann,
On Saturday 17 March 2007 17:50, johann deneux wrote:
> A note about that patch: Apparently Anders Fugmann submitted a patch to use
> usb_kill_urb to linux-usb-devel for version 2.6.10.
> I don't know if this patch got lost, or if it was rejected.
Since every other USB dirver uses usb_kill_urb it loosk like the patch was
just missed...
>
> On 3/17/07, johann deneux <johann.deneux@gmail.com> wrote:
> >
> > commit 0ba8785483c2ee7f56e8f242e000f6cd17a7da40
> > Author: Johann Deneux <johann.deneux@gmail.com>
> > Date: Sat Mar 17 22:23:44 2007 +0100
> >
> > iforce: Use usb_kill_urb instead of usb_unlink_urb.
> >
> > Using usb_unlink_urb can cause iforce_open to fail when called soon
> > after iforce_release.
> > Also updated my email address and replaced calls to printk() by dbg(),
> > warn(), info(), err()...
> >
Since there seems a lot of implementations of r warn(), err(), etc what kind
of output would iforce produce?
--
Dmitry
next prev parent reply other threads:[~2007-03-18 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38b3b7c0703171439n10025a7bx55a588911eb765d6@mail.gmail.com>
2007-03-17 21:43 ` [PATCH] iforce: Use usb_kill_urb instead of usb_unlink_urb johann deneux
2007-03-17 21:50 ` johann deneux
2007-03-18 1:37 ` Dmitry Torokhov [this message]
2007-03-18 8:01 ` johann deneux
2007-03-19 16:18 ` Dmitry Torokhov
2007-03-19 20:49 ` johann deneux
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=200703172137.23385.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=johann.deneux@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-usb-devel@lists.sourceforge.net \
/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.