[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F684407.1040807@suse.cz>
Date: Tue, 20 Mar 2012 09:47:03 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: David Miller <davem@...emloft.net>
CC: Valdis.Kletnieks@...edu, joe@...ches.com, tytso@....edu,
anca.emanuel@...il.com, adilger.kernel@...ger.ca,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/9] ext4: Use pr_fmt and pr_<level>
On 03/20/2012 08:10 AM, David Miller wrote:
> From: Valdis.Kletnieks@...edu
> Date: Tue, 20 Mar 2012 01:46:06 -0400
>
>> OK. Say I'm a scraper. How do I distinguish between:
>>
>> pr_info("foo");
>> printk(KERN_INFO "foo");
>>
>> Oh my. seems that both result in exactly the same thing ending up in the
>> dmesg buffer
>
> No it doesn't result in the same output, read the definitions again.
>
> pr_info can be influenced by pr_fmt, plain printk cannot
Ok, but how exactly does one select per-subsystem messages relying only
on pr_fmt?
Joe writes: "notify a particular set of per subsystem messages that
pr_<level> could easily provide"
Maybe the concept is not explained well enough that we do not follow?
thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists