|| ||Martin Schwidefsky <email@example.com>|
|| ||firstname.lastname@example.org, email@example.com,
|| ||[patch 0/3] [RFC] kmsg macros and script, take x+1.|
|| ||Wed, 30 Jul 2008 18:56:56 +0200|
|| ||Andrew Morton <firstname.lastname@example.org>,
Michael Holzheu <email@example.com>,
Gerrit Huizenga <firstname.lastname@example.org>,
Greg Kroah-Hartman <email@example.com>,
Randy Dunlap <firstname.lastname@example.org>,
Jan Kara <email@example.com>, Pavel Machek <firstname.lastname@example.org>,
Sam Ravnborg <email@example.com>, Joe Perches <firstname.lastname@example.org>,
Kunai Takashi <email@example.com>,
Tim Bird <firstname.lastname@example.org>|
the last kmsg patches on lkml got some useful feedback and Andrew advised
to extend the scope of the this discussion to lf_kernel_messages. I've
added all individuals I could find who participated in the kernel messages
discussions last year.
Since then we continued to work on the kernel messages for s390 and the
three patches in this series is the gist of it.
The lastest changes:
* kmsg.h has been moved from include/asm-s390 to include/linux
* The s390 specific documentation is now in Documentation/kmsg/s390
* The script checks for messages in the source file, Documentation/kmsg
* I've reduced the number of patches to three, a single example how
the kmsg interface is used should be enough.
The initial approach has been to keep the kmsg interface local to s390,
but Andrew thinks it has potential for common use. That is where all
the people on Cc: come into play: what is your opinion? Can we go ahead
"Reality continues to ruin my life." - Calvin.