From: Paulo Marques <pmarques@grupopie.com>
To: Andy Lutomirski <amluto@hotmail.com>
Cc: Greg KH <greg@kroah.com>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [BK PATCH] USB update for 2.6.3
Date: Fri, 20 Feb 2004 15:31:47 +0000 [thread overview]
Message-ID: <40362863.9090109@grupopie.com> (raw)
In-Reply-To: 4035AA75.1060109@hotmail.com
Andy Lutomirski wrote:
> Greg KH wrote:
>
>>
>> Paulo Marques:
>> o USB: fix usblp.c
>>
>
> Unless I'm missing something, this won't fix the usblp_write spinning
> bug I hit. If it helps, I can try to reproduce it with some debugging
> code attached.
>
That is why on our latest thread about this I requested that you tested the
patch to check your bug went way.
My patch *does* correct *a* bug. I tested it myself because I could trigger the
bug easily, and after the patch the bug was gone.
I just wanted you to test if our bugs were different, or on the contrary, they
are in fact the same.
They could be the same, because in my case, the driver would hang sending
garbage to the printer. Because the printer was a dot-matrix "print what it
receives" kind of printer, it would output the garbage continously. If it were a
more "inteligent" printer it might refuse the garbage and not print anything at
all, giving the same result as if nothing was being printed.
Anyway, if the bugs are different, then yes, another patch is needed to fix
"your" bug :)
You will be the best person to do it, since you can trigger the bug, and test a
before / after scenario.
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
next prev parent reply other threads:[~2004-02-20 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.d7mjamc.1l40pri@ifi.uio.no>
2004-02-20 6:34 ` [BK PATCH] USB update for 2.6.3 Andy Lutomirski
2004-02-20 15:31 ` Paulo Marques [this message]
[not found] <fa.ck6rcsq.nl8r18@ifi.uio.no>
[not found] ` <fa.eul0v67.1p62arn@ifi.uio.no>
2004-03-04 18:05 ` [linux-usb-devel] " Andy Lutomirski
2004-02-20 1:28 Greg KH
2004-02-20 5:58 ` Linus Torvalds
2004-02-20 6:03 ` Benjamin Herrenschmidt
2004-02-20 6:30 ` Linus Torvalds
2004-02-20 6:28 ` Benjamin Herrenschmidt
2004-02-20 6:47 ` Linus Torvalds
2004-02-20 6:42 ` Benjamin Herrenschmidt
2004-02-20 7:00 ` Greg KH
2004-02-20 7:58 ` [linux-usb-devel] " David Brownell
2004-02-20 7:03 ` Linus Torvalds
2004-02-20 7:04 ` David S. Miller
2004-02-20 7:10 ` Benjamin Herrenschmidt
2004-02-20 7:32 ` David S. Miller
2004-02-20 15:15 ` Linus Torvalds
2004-02-20 18:15 ` Hollis Blanchard
2004-02-20 18:39 ` Linus Torvalds
2004-02-20 19:20 ` Hollis Blanchard
2004-02-20 19:32 ` Linus Torvalds
2004-02-20 22:40 ` [linux-usb-devel] " Benjamin Herrenschmidt
2004-02-20 19:30 ` Alan Stern
2004-02-20 7:08 ` Benjamin Herrenschmidt
2004-02-20 8:08 ` David Brownell
2004-02-20 9:26 ` Russell King
2004-02-20 7:40 ` Deepak Saxena
2004-02-20 7:47 ` [linux-usb-devel] " Benjamin Herrenschmidt
2004-02-20 8:08 ` Deepak Saxena
2004-02-20 8:43 ` David Brownell
2004-02-20 8:48 ` Benjamin Herrenschmidt
2004-02-20 9:27 ` Russell King
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=40362863.9090109@grupopie.com \
--to=pmarques@grupopie.com \
--cc=amluto@hotmail.com \
--cc=greg@kroah.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