From: Valdis.Kletnieks@vt.edu
To: mingo@redhat.com, peterz@infradead.org
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: 2.6.26-<mumble> question regarding kernel/lockdep.c
Date: Tue, 22 Jul 2008 20:20:10 -0400 [thread overview]
Message-ID: <42591.1216772410@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
I was chasing after some weird behavior with lockdep, and I found that
almost none of the printk() calls in kernel/lockdep.c have a KERN_FOO
level specified.
It looks like it could use patching, but before I code something, I
need to know if the patch should be doing:
a) Adding the missing KERN_FOO levels..
or
b) Adding a comment explaining the subtle reason they're not there...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next reply other threads:[~2008-07-23 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 0:20 Valdis.Kletnieks [this message]
2008-07-28 15:01 ` Ingo Molnar
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=42591.1216772410@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®