From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@xenotime.net>, Andrew Murray <amurray@mpcdata.com>
Cc: wangyanqing <udknight@gmail.com>,
namhyung@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: doc?
Date: Wed, 08 Jun 2011 08:50:05 -0700 [thread overview]
Message-ID: <1307548205.27558.3.camel@Joe-Laptop> (raw)
In-Reply-To: <20110608082548.8ab682fd.rdunlap@xenotime.net>
On Wed, 2011-06-08 at 08:25 -0700, Randy Dunlap wrote:
> On Wed, 8 Jun 2011 10:40:58 +0000 wangyanqing wrote:
> > I can't find the information
> > from Documentation/printk-formats.txt.
> It wouldn't hurt to add some docs, yes, but for now the %p
> extensions are all documented in lib/vsprintf.c, just above
> function pointer(), around line 802 in 3.0-rc2.
Awhile back Andrew Murray proposed a patch.
Maybe he'll get back to it.
https://lkml.org/lkml/2011/2/5/212
next prev parent reply other threads:[~2011-06-08 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 10:40 doc? wangyanqing
2011-06-08 15:25 ` doc? Randy Dunlap
2011-06-08 15:50 ` Joe Perches [this message]
2011-06-09 11:03 ` doc? Andrew Murray
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=1307548205.27558.3.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=amurray@mpcdata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=udknight@gmail.com \
/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