From: Keith Owens <kaos@ocs.com.au>
To: "Ph. Marek" <philipp.marek@bmlv.gv.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: printk() without KERN_ prefixes? (in 2.5.59) and Q: small kernel image doc
Date: Tue, 21 Jan 2003 20:23:20 +1100 [thread overview]
Message-ID: <12940.1043141000@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 21 Jan 2003 09:58:43 BST." <200301210930.14551.philipp.marek@bmlv.gv.at>
On Tue, 21 Jan 2003 09:58:43 +0100,
"Ph. Marek" <philipp.marek@bmlv.gv.at> wrote:
>Should they be fixed to KERN_INFO or some such? I'm willing to contribute a
>patch (which will be done by script, of course). Or am I missing something
>and they shall stay as they are?
Do not blindly add KERN_*. Some prints are done with multiple calls to
printk(), only the first call should have KERN_*, otherwise you get
lines like this, with embedded '<n>' strings.
/dev/xscsi/pci01.00.0-1/target0/lun0:<6> p1<6> p2<6> p3<6> p4 <<6> p5<6> p6<6> p7 >
next prev parent reply other threads:[~2003-01-21 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 8:58 Ph. Marek
2003-01-21 9:23 ` Keith Owens [this message]
2003-01-24 11:32 ` [PATCH available] Re: printk() without KERN_ prefixes? (in 2.5.59) Ph. Marek
2003-02-12 15:10 ` [PATCHes] printk() without KERN_ prefixes for 2.5.60 Ph. Marek
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=12940.1043141000@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.marek@bmlv.gv.at \
/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®