From: Willy Tarreau <w@1wt.eu>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Benjamin Cherian <benjamin.cherian.kernel@gmail.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, mtosatti@redhat.com
Subject: Re: Bug with USB proc_bulk in 2.4 kernel
Date: Tue, 25 Jul 2006 21:31:40 +0200 [thread overview]
Message-ID: <20060725193140.GK2037@1wt.eu> (raw)
In-Reply-To: <20060724230732.4fdf2bf4.zaitcev@redhat.com>
Hi Pete,
On Mon, Jul 24, 2006 at 11:07:32PM -0700, Pete Zaitcev wrote:
> On Thu, 20 Jul 2006 10:43:59 -0700, Benjamin Cherian <benjamin.cherian.kernel@gmail.com> wrote:
>
> > > Although I am starting to think about creating a custom locking
> > > scheme in devio.c after all. It seems like less work.
>
> > What's your timeframe for this? Good luck with it.
>
> OK, now I hate my life, I hate you, I hate Stuart, but most of all
> I hate the anonymous Japanese who wrote the microcode for TEAC CD-210PU.
> Anyway, please test the attached patch. Does it do what you want?
I'm very glad that you're still maintaining 2.4 code so much actively. Do
you think of any possible side effects that non-TEAC users might encounter ?
If you feel more comfortable after some particular corner-case tests on other
hardware, please ask.
> -- Pete
Cheers,
Willy
next prev parent reply other threads:[~2006-07-25 19:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1152332281.24203.linux-kernel2news@redhat.com>
2006-07-08 20:28 ` Bug with USB proc_bulk in 2.4 kernel and possibly bug in proc_ioctl in 2.6 Pete Zaitcev
2006-07-10 19:58 ` Bug with USB proc_bulk in 2.4 kernel Benjamin Cherian
2006-07-10 20:40 ` Pete Zaitcev
2006-07-17 21:35 ` Benjamin Cherian
2006-07-17 22:19 ` Pete Zaitcev
2006-07-18 17:04 ` Benjamin Cherian
2006-07-19 1:33 ` Pete Zaitcev
2006-07-20 17:43 ` Benjamin Cherian
2006-07-25 6:07 ` Pete Zaitcev
2006-07-25 19:31 ` Willy Tarreau [this message]
2006-07-27 22:21 ` Benjamin Cherian
2006-07-27 23:49 ` Pete Zaitcev
2006-07-28 17:37 ` Benjamin Cherian
2006-07-30 7:35 ` Pete Zaitcev
2006-07-31 18:41 ` Benjamin Cherian
2006-08-02 19:51 ` Willy Tarreau
2006-08-03 1:02 ` Pete Zaitcev
2006-08-03 2:33 ` Willy Tarreau
2006-08-03 6:00 ` Pete Zaitcev
2006-08-03 6:29 ` Willy Tarreau
2006-08-04 16:57 ` Benjamin Cherian
2006-08-04 16:55 ` Willy Tarreau
2006-08-09 17:01 ` Benjamin Cherian
2006-08-09 17:02 ` Willy Tarreau
2006-08-12 0:14 ` Marcelo Tosatti
2006-08-12 3:21 ` Willy Tarreau
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=20060725193140.GK2037@1wt.eu \
--to=w@1wt.eu \
--cc=benjamin.cherian.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mtosatti@redhat.com \
--cc=zaitcev@redhat.com \
/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