[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3ece790808142233y3150b4d1sfeaa0342dbac31a6@mail.gmail.com>
Date: Thu, 14 Aug 2008 22:33:10 -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 Thu, Aug 14, 2008 at 8:44 PM, Greg KH <gregkh@...e.de> wrote:
>
> What is wrong with what we have already agreed to standardise on here
> people? dev_printk() for devices! It uniquely shows the device, what
> driver is bound to it (if any), the bus id, and everything else.
Part of the problem, imho, is the "if any" part. But I am more than happy to
build on existing solutions. All the world is not a dev, though. 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.
Tim
--
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