From: Joe Perches <joe@perches.com>
To: Christopher Sacchi <christophersacchi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Kernel Oops Priority Level in <linux/printk.h>
Date: Tue, 28 May 2013 15:15:15 -0700 [thread overview]
Message-ID: <1369779315.22004.81.camel@joe-AO722> (raw)
In-Reply-To: <CABQQNFFAxX3jV4h83g1bhNkwEu2=4R2kqk4E5QAPirB=N3dTAw@mail.gmail.com>
On Tue, 2013-05-28 at 18:08 -0400, Christopher Sacchi wrote:
> Here is a patch for linux-3.10-rc2 that adds a KERN_OOPS priority
> level as a handler for if a kernel oops occurs, (this priority can be
> used for a message to the kernel log,) and it is applied to
> linux/printk.h in the include directory. It has been checked and has 2
[]
> +++ include/linux/printk.h 2013-05-28 17:39:21.530055578 -0400
> @@ -395,4 +395,8 @@ static inline void print_hex_dump_bytes(
[]
> +/* Define an oops priority level. */
> +#define pr_oops(fmt, ...) \
> + printk(KERN_OOPS pr_fmt(fmt), ##__VA_ARGS__)
> +
> #endif
Why? Why not KERN_DEFAULT?
Where is KERN_OOPS #defined?
prev parent reply other threads:[~2013-05-28 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 22:08 Christopher Sacchi
2013-05-28 22:09 ` Christopher Sacchi
2013-05-28 22:13 ` Christopher Sacchi
2013-05-28 22:15 ` Joe Perches [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=1369779315.22004.81.camel@joe-AO722 \
--to=joe@perches.com \
--cc=christophersacchi@gmail.com \
--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
all inboxes | Powered by JetHome®