From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] loglevel=pci:8,acpi:8,apic=8 support v5
Date: Wed, 17 Sep 2008 11:10:58 -0700 [thread overview]
Message-ID: <86802c440809171110y3b91e27q382c6ee7bcd58c28@mail.gmail.com> (raw)
In-Reply-To: <48D13960.2020902@zytor.com>
On Wed, Sep 17, 2008 at 10:07 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> Ingo Molnar wrote:
>>
>> the subsystem tags should be cut out by dmesg by default, just like the
>> normal <1> tags are cut out.
>>
> [...]
>>
>> and it's bad and a showstopper if the default output of 'dmesg' degrades,
>> like your noticed - those are bugs in the concept and need to be fixed.
>>
>
> It's probably worth pointing out that we had similar transition pains when
> we introduced the loglevel tags. If you used an old dmesg/klogd you got the
> loglevel tags; we cleaned them up.
want to expand loglevel tags to two digi bits, hope the dmesg/klogd
could handle it.
YH
next prev parent reply other threads:[~2008-09-17 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 7:10 Yinghai Lu
2008-09-17 7:10 ` [PATCH 1/6] add DEFINE_LOGLEVEL_SETUP v6 Yinghai Lu
2008-09-17 7:10 ` [PATCH 2/6] pci: add KERN_PCI Yinghai Lu
2008-09-17 7:10 ` [PATCH 3/6] pci: using printk(KERN_PCI v3 Yinghai Lu
2008-09-17 7:10 ` [PATCH 4/6] acpi: add KERN_ACPI v3 Yinghai Lu
2008-09-17 7:10 ` [PATCH 5/6] apci: dump slit with printk(KERN_ACPI...) Yinghai Lu
2008-09-17 7:10 ` [PATCH 6/6] x86: add KERN_APIC Yinghai Lu
2008-09-17 7:30 ` [PATCH 0/6] loglevel=pci:8,acpi:8,apic=8 support v5 Alexey Dobriyan
2008-09-17 8:47 ` Ingo Molnar
2008-09-17 9:25 ` Alexey Dobriyan
2008-09-17 9:40 ` Ingo Molnar
2008-09-17 16:23 ` Yinghai Lu
2008-09-17 17:07 ` H. Peter Anvin
2008-09-17 18:10 ` Yinghai Lu [this message]
2008-09-17 18:17 ` H. Peter Anvin
2008-09-17 19:05 ` 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=86802c440809171110y3b91e27q382c6ee7bcd58c28@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.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®