From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: netdev@vger.kernel.org, Karsten Keil <kkeil@suse.de>
Subject: strange inconsistency in printk's
Date: Sat, 17 May 2008 05:53:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805170551290.5409@localhost.localdomain> (raw)
part of the output from one of my scanning scripts:
...
drivers/net/bsd_comp.c: printk ("<9>ppp: lens_ptr(%d) > max\n", idx);
drivers/net/bsd_comp.c: printk ("<9>ppp: dict_ptr(%d) > max\n", idx);
drivers/isdn/i4l/isdn_bsdcomp.c: printk (KERN_DEBUG "<9>ppp: lens_ptr(%d) > max\n", idx);
drivers/isdn/i4l/isdn_bsdcomp.c: printk (KERN_DEBUG "<9>ppp: dict_ptr(%d) > max\n", idx);
...
is there a reason that a pair of those have a printk level of
KERN_DEBUG while the others don't? it just looks a bit weird.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
reply other threads:[~2008-05-17 9:53 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=alpine.LFD.1.10.0805170551290.5409@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=kkeil@suse.de \
--cc=netdev@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).