Re: Documentation of kernel messages (Summary)
- From: Michael Holzheu <holzheu@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Jun 2007 17:11:19 +0200
On Mon, 2007-06-25 at 11:44 -0400, Rob Landley wrote:
On Monday 25 June 2007 09:48:41 Michael Holzheu wrote:
Hi all,
Any idea, how to proceed with this topic? Do you think that any of the
suggested solutions for documentation / translation of kernel messages
will have a chance to be included in the kernel?
Personally? No to the second question, which renders the first "do it
yourself outside of the tree".
If that is the opinion of the majority here, fine. If there is no hard
rule on how to define printk macros, one option for us would be to
define some new s390 specific printk macros for our device drivers.
Similar to hundreds of other driver specific printk macros in the
kernel.
Just a guess, and I don't speak for anyone else here, but I think most of us
are waiting to see how long it takes you to lose interest.
:-) Work is not always fun. Sometimes it is just a duty.
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [RFC/PATCH] Documentation of kernel messages
- From: holzheu
- Re: [RFC/PATCH] Documentation of kernel messages
- From: Andrew Morton
- Documentation of kernel messages (Summary)
- From: Michael Holzheu
- Re: Documentation of kernel messages (Summary)
- From: Rob Landley
- [RFC/PATCH] Documentation of kernel messages
- Prev by Date: Re: [PATCH] trim memory not covered by WB MTRRs
- Next by Date: Re: [AppArmor 00/44] AppArmor security module overview
- Previous by thread: Re: Documentation of kernel messages (Summary)
- Next by thread: [Processor] Hi-Temperature showed in trip points
- Index(es):
Relevant Pages
|