public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Flory <sflory@rackable.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Pete de Zwart <dezwart@froob.net>,
	Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: 2.4.19: drivers/usb/printer.c usblpX on fire
Date: 09 Aug 2002 10:10:56 -0700	[thread overview]
Message-ID: <1028913064.1380.493.camel@flory.corp.rackablelabs.com> (raw)
In-Reply-To: <15699.31589.634056.607809@kim.it.uu.se>

On Fri, 2002-08-09 at 01:20, Mikael Pettersson wrote:
> Pete de Zwart writes:
>  > Is there a reason that in 2.4.19's drivers/usb/printer.c if the printer status
>  > code from is greater than 2 it states that it is on fire instead of printing
>  > the unknown error code?
> 
> Dunno, but the parport lp.c also goes into "printer on fire" mode, in my case
> whenever the black ink cartridge becomes empty :-(
> 


  The printer on fire message is the traditional Un*x error message for
unknown error on a printer.



  reply	other threads:[~2002-08-09 17:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09  6:03 2.4.19: drivers/usb/printer.c usblpX on fire Pete de Zwart
2002-08-09  8:20 ` Mikael Pettersson
2002-08-09 17:10   ` Samuel Flory [this message]
2002-08-09 20:44     ` Pete de Zwart
2002-08-13  2:53       ` Bill Davidsen
2002-08-11 20:18     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-08-09 22:00 Jesse Pollard
2002-08-11  0:03 ` Pete de Zwart
2002-08-11  0:52   ` Brad Hards
2002-08-11  1:36     ` Pete de Zwart
2002-08-11  3:30       ` Brad Hards

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=1028913064.1380.493.camel@flory.corp.rackablelabs.com \
    --to=sflory@rackable.com \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=dezwart@froob.net \
    --cc=mikpe@csd.uu.se \
    /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