[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1369779315.22004.81.camel@joe-AO722>
Date: Tue, 28 May 2013 15:15:15 -0700
From: Joe Perches <joe@...ches.com>
To: Christopher Sacchi <christophersacchi@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH]: Kernel Oops Priority Level in <linux/printk.h>
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists