From: Riley Williams <rhw@moo.cus.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Obviously-correct patch to 2.2.17
Date: Sat, 28 Oct 2000 10:29:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010281028310.11719-200000@moo.cus.org.uk> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1451 bytes --]
Hi Alan.
This patch simply corrects a couple of comments in the said file to
reflect what the code actually does rather than (presumably) what the
code used to do at some time in the distant past.
In my case, I've been working on a patch for the kernel that uses
these facilities, and was getting confused because of the discrepancy
between what the comments say and what actually happens. It wasn't
until I realised that the comments were just plain wrong that I was
able to sort the thing out, so I'm submitting this patch to prevent
others having the same problem.
Incidentally, the code as it stands actually simplifies the patch I
was working on considerably, and I regard this as a useful feature as
a result.
I don't have the latest 2.4-pre kernel to hand to check, but it's
quite likely that this patch can also be applied to that with the same
results.
Best wishes from Riley.
* Copyright (C) 2000, Memory Alpha Systems.
* All rights and wrongs reserved.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* http://www.memalpha.cx/Linux/Kernel/
[-- Attachment #2: Patch to kernel/printk.c --]
[-- Type: TEXT/PLAIN, Size: 713 bytes --]
--- linux-2.2.17/kernel/printk.c~ Wed Oct 27 01:53:42 1999
+++ linux-2.2.17/kernel/printk.c Sat Oct 28 10:01:20 2000
@@ -109,12 +109,12 @@
* Commands to do_syslog:
*
* 0 -- Close the log. Currently a NOP.
* 1 -- Open the log. Currently a NOP.
* 2 -- Read from the log.
- * 3 -- Read up to the last 4k of messages in the ring buffer.
+ * 3 -- Read all messages remaining in the ring buffer.
- * 4 -- Read and clear last 4k of messages in the ring buffer
+ * 4 -- Read and clear all messages remaining in the ring buffer
* 5 -- Clear ring buffer.
* 6 -- Disable printk's to console
* 7 -- Enable printk's to console
* 8 -- Set level of messages printed to console
*/
reply other threads:[~2000-10-28 9:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.21.0010281028310.11719-200000@moo.cus.org.uk \
--to=rhw@moo.cus.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).