From: Pete de Zwart <dezwart@froob.net>
To: Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: 2.4.19: drivers/usb/printer.c usblpX on fire
Date: Sun, 11 Aug 2002 10:03:40 +1000 [thread overview]
Message-ID: <20020811000340.GF27819@niflheim> (raw)
In-Reply-To: <200208092200.RAA34736@tomcat.admin.navo.hpc.mil>
Cool, thanx Jesse, I always wondered what the history was behind it and
how to achieve it.
Here is another query:
If each printer had their own set of error codes, what would be the way to
implement their display from the kernel?
Would each printer have to have their own module if they had a non-standard
list of error codes or would we simply ignore them and state that the
ill conforming printer is on fire?
Pete de Zwart.
--
The real reason your computer crashed, thanx to the BOFH:
"Your processor does not develop enough heat."
next prev parent reply other threads:[~2002-08-11 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 22:00 2.4.19: drivers/usb/printer.c usblpX on fire Jesse Pollard
2002-08-11 0:03 ` Pete de Zwart [this message]
2002-08-11 0:52 ` Brad Hards
2002-08-11 1:36 ` Pete de Zwart
2002-08-11 3:30 ` Brad Hards
-- strict thread matches above, loose matches on Subject: below --
2002-08-09 6:03 Pete de Zwart
2002-08-09 8:20 ` Mikael Pettersson
2002-08-09 17:10 ` Samuel Flory
2002-08-09 20:44 ` Pete de Zwart
2002-08-13 2:53 ` Bill Davidsen
2002-08-11 20:18 ` Alan Cox
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=20020811000340.GF27819@niflheim \
--to=dezwart@froob.net \
--cc=Linux-Kernel@vger.kernel.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