From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Marcin Slusarz" <marcin.slusarz@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] add DEFINE_LOGLEVEL_SETUP v3
Date: Tue, 16 Sep 2008 14:04:33 -0700 [thread overview]
Message-ID: <86802c440809161404v4b59f1c8se1ac61f982a15dd@mail.gmail.com> (raw)
In-Reply-To: <20080916190224.GA6115@joi>
On Tue, Sep 16, 2008 at 12:02 PM, Marcin Slusarz
<marcin.slusarz@gmail.com> wrote:
> On Tue, Sep 16, 2008 at 11:01:21AM -0700, Yinghai Lu wrote:
>> --- linux-2.6.orig/include/linux/kernel.h
>> +++ linux-2.6/include/linux/kernel.h
>> @@ -104,6 +104,15 @@ extern int console_printk[];
>> #define minimum_console_loglevel (console_printk[2])
>> #define default_console_loglevel (console_printk[3])
>>
>> +#define KERN_LOG_EMERG 0 /* system is unusable */
>> +#define KERN_LOG_ALERT 1 /* action must be taken immediately */
>> +#define KERN_LOG_CRIT 2 /* critical conditions */
>> +#define KERN_LOG_ERR 3 /* error conditions */
>> +#define KERN_LOG_WARNING 4 /* warning conditions */
>> +#define KERN_LOG_NOTICE 5 /* normal but significant condition */
>> +#define KERN_LOG_INFO 6 /* informational */
>> +#define KERN_LOG_DEBUG 7 /* debug-level messages */
>> +
>> struct completion;
>> struct pt_regs;
>> struct user;
>
> maybe
> #define KERN_LOG_EMERG 0,KERN_EMERG
> #define KERN_LOG_ALERT 1,KERN_ALERT
> ...
> ?
>
> or better - create printk2(level, fmt) which prints "<", level, ">", fmt
> and wrap it with pci_printk / acpi_printk?
>
will come out one new version that hpa likes
printk(KERN_PCI KERN_DEBUG "sadfasf\n");
YH
next prev parent reply other threads:[~2008-09-16 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 18:01 [PATCH 0/5] loglevel=pci:7,acpi:6 support Yinghai Lu
2008-09-16 18:01 ` [PATCH 1/5] add DEFINE_LOGLEVEL_SETUP v3 Yinghai Lu
2008-09-16 19:02 ` Marcin Slusarz
2008-09-16 21:04 ` Yinghai Lu [this message]
2008-09-16 21:18 ` H. Peter Anvin
2008-09-16 21:28 ` Yinghai Lu
2008-09-16 21:55 ` H. Peter Anvin
2008-09-16 18:01 ` [PATCH 2/5] pci: add pci_printk v3 Yinghai Lu
2008-09-16 18:01 ` [PATCH 3/5] pci: using pci_printk Yinghai Lu
2008-09-16 18:01 ` [PATCH 4/5] acpi: add acpi_printk v2 Yinghai Lu
2008-09-16 18:01 ` [PATCH 5/5] apci: dump slit v3 Yinghai Lu
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=86802c440809161404v4b59f1c8se1ac61f982a15dd@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®