The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: John Carlson <carlsj@yahoo.com>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] Usb gadget drivers 2.4 kernel
Date: Tue, 15 Jun 2004 17:13:57 -0700	[thread overview]
Message-ID: <40CF90C5.7050907@pacbell.net> (raw)
In-Reply-To: <20040614133218.53174.qmail@web41013.mail.yahoo.com>

John Carlson wrote:
> While developing a gadget driver for the 2.4 kernel, I
> discovered this error in the gadget driver.  This bug
> has been present since the gadget driver was back
> ported from the 2.6 kernel.

Actually, it's just that one source file (config.c),
and the fix is in the gadget-2.4 tree already.  I'll
have to resubmit this one, it's rather annoying to
anyone trying to make sure their new hardware works!

- Dave




      reply	other threads:[~2004-06-16  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 13:32 [PATCH] Usb gadget drivers 2.4 kernel John Carlson
2004-06-16  0:13 ` David Brownell [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=40CF90C5.7050907@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=carlsj@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox