From: Tim Waugh <twaugh@redhat.com>
To: Peter Osterlund <peter.osterlund@mailbox.swipnet.se>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Printing to off-line printer in 2.4.0-prerelease
Date: Thu, 4 Jan 2001 21:52:10 +0000 [thread overview]
Message-ID: <20010104215210.D1148@redhat.com> (raw)
In-Reply-To: <m2k88czda4.fsf@ppro.localdomain> <20010104112027.G23469@redhat.com> <20010104145229.E17640@athlon.random> <20010104142043.N23469@redhat.com> <m21yujuoew.fsf@ppro.localdomain>
In-Reply-To: <m21yujuoew.fsf@ppro.localdomain>; from peter.osterlund@mailbox.swipnet.se on Thu, Jan 04, 2001 at 08:07:19PM +0100
On Thu, Jan 04, 2001 at 08:07:19PM +0100, Peter Osterlund wrote:
> If you do this, you should probably also return -EAGAIN if the printer
> is out of paper, otherwise I would still lose data when the printer
> goes out of paper. Currently it returns -ENOSPC in this situation. I
> suppose the different return codes were meant as a way for user space
> to be able to know why printing failed, so that it could take
> appropriate actions, but maybe this is not used by any programs.
They were intended for that, yes, but it's probably better to stick
with the 2.2 return codes. Here's a patch to do that. Look okay?
Tim.
*/
2001-01-04 Tim Waugh <twaugh@redhat.com>
* drivers/char/lp.c: Follow 2.2 behaviour more closely.
--- linux-2.4.0-prerelease/drivers/char/lp.c.offline Thu Jan 4 21:13:02 2001
+++ linux-2.4.0-prerelease/drivers/char/lp.c Thu Jan 4 21:42:19 2001
@@ -207,7 +207,7 @@
last = LP_POUTPA;
printk(KERN_INFO "lp%d out of paper\n", minor);
}
- error = -ENOSPC;
+ error = -EIO;
} else if (!(status & LP_PSELECD)) {
if (last != LP_PSELECD) {
last = LP_PSELECD;
@@ -230,7 +230,10 @@
if (last != 0)
lp_error(minor);
- return error;
+ if (LP_F (minor) & LP_ABORT)
+ return error;
+
+ return 0;
}
static ssize_t lp_write(struct file * file, const char * buf,
@@ -292,7 +295,7 @@
/* incomplete write -> check error ! */
int error = lp_check_status (minor);
- if (LP_F(minor) & LP_ABORT) {
+ if (error) {
if (retv == 0)
retv = error;
break;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-04 21:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 18:44 Printing to off-line printer in 2.4.0-prerelease Peter Osterlund
2001-01-03 19:13 ` Andrea Arcangeli
2001-01-03 21:00 ` Peter Osterlund
2001-01-03 21:35 ` Andrea Arcangeli
2001-01-04 0:08 ` Peter Osterlund
2001-01-04 0:41 ` Andrea Arcangeli
2001-01-04 1:09 ` Peter Osterlund
2001-01-04 1:39 ` Andrea Arcangeli
2001-01-04 11:17 ` Tim Waugh
2001-01-04 9:27 ` Tim Waugh
2001-01-04 13:50 ` Andrea Arcangeli
2001-01-04 11:20 ` Tim Waugh
2001-01-04 13:52 ` Andrea Arcangeli
2001-01-04 14:20 ` Tim Waugh
2001-01-04 14:39 ` Andrea Arcangeli
2001-01-04 14:54 ` Tim Waugh
2001-01-04 19:45 ` Peter Osterlund
2001-01-04 19:07 ` Peter Osterlund
2001-01-04 21:52 ` Tim Waugh [this message]
2001-01-05 0:33 ` Peter Osterlund
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 15:30 Jesse Pollard
2001-01-04 19:22 ` Gunther Mayer
2001-01-05 1:13 ` Jesse Pollard
2001-01-04 23:20 ` David Ford
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=20010104215210.D1148@redhat.com \
--to=twaugh@redhat.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.osterlund@mailbox.swipnet.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