[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3ir9q6hyz.fsf@maximus.localdomain>
Date: Thu, 14 Jun 2007 10:47:00 +0200
From: Krzysztof Halasa <khc@...waw.pl>
To: holzheu@...ux.vnet.ibm.com
Cc: Valdis.Kletnieks@...edu, linux-kernel@...r.kernel.org,
randy.dunlap@...cle.com, akpm@...l.org, gregkh@...e.de,
mtk-manpages@....net, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com
Subject: Re: [RFC/PATCH] Documentation of kernel messages
Hi,
holzheu <holzheu@...ux.vnet.ibm.com> writes:
> If the information is to big for the printk itself, because you would
> need 10 lines to explain what happened, wouldn't it be good to have a
> place where to put that information?
I think if a message really has to be 10 lines long to be clear then
it should just be 10 lines long. The keyword is "really".
Example: oops.
--
Krzysztof Halasa
-
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