From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Add kerneldoc documentation for new printk format extensions
Date: Tue, 7 Oct 2008 11:33:05 +0100 [thread overview]
Message-ID: <20081007103305.GH2886@hack.voiplan.pt> (raw)
In-Reply-To: <20081007101532.GA25565@basil.nowhere.org>
On Tue, Oct 07, 2008 at 12:15:32PM +0200, Andi Kleen wrote:
>Add documentation in kerneldoc for new printk format extensions
>
>This patch documents the new %pS/%pF options in printk in kernel doc.
>
>Hope I didn't miss any other extension.
>
>Signed-off-by: Andi Kleen <ak@linux.intel.com>
>
>Index: linux-2.6.27-rc6-misc/kernel/printk.c
>===================================================================
>--- linux-2.6.27-rc6-misc.orig/kernel/printk.c
>+++ linux-2.6.27-rc6-misc/kernel/printk.c
>@@ -593,6 +593,8 @@ static int have_callable_console(void)
> *
> * See also:
> * printf(3)
>+ *
>+ * See the vsnprintf() documentation for format string extensions over C99.
> */
>
> asmlinkage int printk(const char *fmt, ...)
>Index: linux-2.6.27-rc6-misc/lib/vsprintf.c
>===================================================================
>--- linux-2.6.27-rc6-misc.orig/lib/vsprintf.c
>+++ linux-2.6.27-rc6-misc/lib/vsprintf.c
>@@ -565,6 +565,10 @@ static char *pointer(const char *fmt, ch
> * @fmt: The format string to use
> * @args: Arguments for the format string
> *
>+ * This function follows C99 vsnprintf, but has some extensions:
>+ * %pS output the name of a text symbol
>+ * %pF output the name of a function pointer
s/output/outputs/ ? :)
--
"Sometimes the only way to stay sane is to go a little crazy."
next prev parent reply other threads:[~2008-10-07 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 10:15 [PATCH] Add kerneldoc documentation for new printk format extensions Andi Kleen
2008-10-07 10:33 ` Américo Wang [this message]
2008-10-07 11:14 ` Andi Kleen
2008-10-07 15:58 ` Randy.Dunlap
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=20081007103305.GH2886@hack.voiplan.pt \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
/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