From: Cory Watson <gphat@cafes.net>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Re: [PATCH] Add KERN_* constants to printk()s
Date: Wed, 26 Jun 2002 20:25:03 -0500 [thread overview]
Message-ID: <auto-000061790465@dc-mx13.cluster1.charter.net> (raw)
In-Reply-To: <auto-000059811429@dc-mx08.cluster1.charter.net>
Apologies, this is for 2.5.24...
On Wednesday 26 June 2002 08:19 pm, Cory Watson wrote:
> From Kernel-Janitor todo, make sure printk() calls have the appropriate
> KERN_* constant. These are only from the kernel/ subdir.
>
> Some of these might be off by a level, but I gave them the level that
> looked appropriate. If this is accepted, I'll do more of them. This is a
> good excercise for newbies like myself ;)
>
> Thanks
--
Cory 'G' Watson
+ Hack, lest ye rust.
prev parent reply other threads:[~2002-06-27 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 1:19 Cory Watson
2002-06-27 1:25 ` Cory Watson [this message]
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=auto-000061790465@dc-mx13.cluster1.charter.net \
--to=gphat@cafes.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®