public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Marcin Slusarz <marcin.slusarz@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	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:55:39 -0700	[thread overview]
Message-ID: <48D02B5B.9090204@zytor.com> (raw)
In-Reply-To: <86802c440809161428j2dfc9669g229a5bf23da63f34@mail.gmail.com>

Yinghai Lu wrote:
> On Tue, Sep 16, 2008 at 2:18 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> Yinghai Lu wrote:
>>> will come out one new version that hpa likes
>>>
>>> printk(KERN_PCI KERN_DEBUG "sadfasf\n");
>>>
>> Come to think about it, it might help migration pains if we put the prefixes
>> in the opposite order (KERN_DEBUG KERN_PCI).
>>
> according to the code flow, these two is the same... will double check it.
> 

The difference is that things that read the kernel log in userspace will 
be able to make partial sense of the latter, but not the former.  It 
will thus make the transition smoother.

	-hpa

  reply	other threads:[~2008-09-16 21:56 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
2008-09-16 21:18       ` H. Peter Anvin
2008-09-16 21:28         ` Yinghai Lu
2008-09-16 21:55           ` H. Peter Anvin [this message]
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=48D02B5B.9090204@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.com \
    /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