From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, jbaron <jbaron@redhat.com>
Subject: Re: [PATCH] introduce boot_printk()
Date: Tue, 16 Sep 2008 09:42:36 -0700 [thread overview]
Message-ID: <86802c440809160942w601691fbnb70a989acc5d98d3@mail.gmail.com> (raw)
In-Reply-To: <48CFD97C.6080002@zytor.com>
On Tue, Sep 16, 2008 at 9:06 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> Peter Zijlstra wrote:
>>>
>>> every subsystem will have
>>> x86_printk
>>> acpi_printk
>>> pci_printk
>>
>> doesn't sound like an easily extensible interface, better would be
>> extending printk with a KERN_subsys tag like proposed.
>>
>
> That would be my thinking too.
will be printk(KERN_PCI, KERN_DEBUG ".....") ?
and it will be ...KERN_PCI will be int?
YH
next prev parent reply other threads:[~2008-09-16 16:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 8:05 Yinghai Lu
2008-09-15 9:58 ` Pavel Machek
2008-09-15 16:14 ` Yinghai Lu
2008-09-15 14:54 ` Randy Dunlap
2008-09-15 17:15 ` H. Peter Anvin
2008-09-15 17:18 ` Yinghai Lu
2008-09-15 17:24 ` H. Peter Anvin
2008-09-15 17:34 ` Yinghai Lu
2008-09-16 14:26 ` Peter Zijlstra
2008-09-16 16:06 ` H. Peter Anvin
2008-09-16 16:42 ` Yinghai Lu [this message]
2008-09-16 17:44 ` Jeremy Fitzhardinge
2008-09-16 17:45 ` Yinghai Lu
2008-09-16 17:47 ` Yinghai Lu
2008-09-16 17:53 ` H. Peter Anvin
2008-09-16 18:10 ` Yinghai Lu
2008-09-16 18:15 ` H. Peter Anvin
2008-09-16 18:24 ` Yinghai Lu
2008-09-16 18:31 ` H. Peter Anvin
2008-09-16 18:37 ` Yinghai Lu
2008-09-16 18:53 ` H. Peter Anvin
2008-09-16 19:24 ` 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=86802c440809160942w601691fbnb70a989acc5d98d3@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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®