From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Theodore Tso <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [GIT PULL/RESEND] kernel message catalog patches
Date: Tue, 28 Oct 2008 09:25:56 +0100 [thread overview]
Message-ID: <1225182356.15745.2.camel@localhost> (raw)
In-Reply-To: <20081027092739.04b89526.randy.dunlap@oracle.com>
On Mon, 2008-10-27 at 09:27 -0700, Randy Dunlap wrote:
> As I said a few months ago, please make it "almost kernel-doc style"
> but something that can be distinguished from the current kernel-doc.
> They aren't quite the same thing AFAICT.
The current format is this:
/*?
* Tag: <component>.<hash>
* Text: "<kmsg message text>"
* Severity: <severity>
* Parameter:
* @1: <description of the first message parameter>
* @2: <description of the second message parameter>
* ...
* Description:
* <What is the kmsg message all about>
* User action:
* <What can the user do to fix the problem>
*/
See the "/*?" vs "/**" ? The kmsg comments are kernel-doc style but not
the same as kernel-doc.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-10-28 8:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 14:50 [GIT PULL] kernel message catalog patches Martin Schwidefsky
2008-10-17 7:59 ` Martin Schwidefsky
2008-10-21 9:21 ` [GIT PULL/RESEND] " Heiko Carstens
2008-10-23 15:35 ` Linus Torvalds
2008-10-23 21:04 ` Heiko Carstens
2008-10-23 21:37 ` Linus Torvalds
2008-10-24 15:50 ` Heiko Carstens
2008-10-26 19:26 ` Martin Schwidefsky
2008-10-26 19:12 ` Linus Torvalds
2008-10-27 10:01 ` Martin Schwidefsky
2008-10-27 15:05 ` Linus Torvalds
2008-10-27 15:52 ` Martin Schwidefsky
2008-10-27 16:19 ` Theodore Tso
2008-10-27 16:27 ` Randy Dunlap
2008-10-28 8:25 ` Martin Schwidefsky [this message]
2008-10-27 16:03 ` Alan Cox
2008-10-27 16:10 ` Linus Torvalds
2008-10-27 16:35 ` Alan Cox
2008-10-27 19:36 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1225182356.15745.2.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox