[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3ece790808151003o24e518a1ra217010f6658c2c6@mail.gmail.com>
Date: Fri, 15 Aug 2008 10:03:16 -0700
From: "Tim Hockin" <thockin@...kin.org>
To: "Greg KH" <gregkh@...e.de>
Cc: "Joe Perches" <joe@...ches.com>, schwidefsky@...ibm.com,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
lf_kernel_messages@...ts.linux-foundation.org,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Michael Holzheu" <holzheu@...ibm.com>,
"Gerrit Huizenga" <gh@...ibm.com>,
"Randy Dunlap" <randy.dunlap@...cle.com>,
"Jan Kara" <jack@...e.cz>, "Pavel Machek" <pavel@....cz>,
"Sam Ravnborg" <sam@...nborg.org>,
"Jochen Voß" <jochen.voss@...glemail.com>,
"Kunai Takashi" <kunai@...ux-foundation.jp>,
"Tim Bird" <tim.bird@...sony.com>
Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros.
On Fri, Aug 15, 2008 at 9:03 AM, Greg KH <gregkh@...e.de> wrote:
>> I'd like to be able to report something like an OOM kill in (roughly)
>> the same way as an ATA error, and I want (though could be talked out
>> of) a way to tell these "events" (for lack of a better word) apart
>> from plain-old-printk()s.
>
> That's great, then create something that can handle both! Don't throw
> away some wonderful information that way over half the kernel has access
> to just because the minority doesn't. That would mean that we would
> loose information in those drivers overall.
Sorry, I never meant to imply that dev_printk() was to be ignored, my
examples was meant to be trivial to demonstrate :) dev_printk() is
good. We should keep it :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists