From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Martin Kletzander <mkletzan@redhat.com>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Stephen Boyd <sboyd@codeaurora.org>, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib: Documentation: Synchronize %p formatting documentation
Date: Tue, 22 Sep 2015 20:40:03 +0200 [thread overview]
Message-ID: <87si66qovw.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <1442827087.8361.117.camel@linux.intel.com> (Andy Shevchenko's message of "Mon, 21 Sep 2015 12:18:07 +0300")
On Mon, Sep 21 2015, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Mon, 2015-09-21 at 11:13 +0200, Martin Kletzander wrote:
>
>> Move all pointer-formatting documentation to one place instead of
>> keeping it in three places with different level of completeness.
I've had a patch titled "vsnprintf: collect documentation in one place"
lying in a misc_printf branch for a while now, so I certainly like this.
> I think we still need at least one in the code. I, for example, often
> read it from the actual c-file, not from documentation.
I'd really prefer actually collecting it in that single place, under
Documentation/, but I guess eliminating one redundant copy is better
than nothing...
Rasmus
next prev parent reply other threads:[~2015-09-22 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 9:13 [PATCH] lib: Documentation: Synchronize %p formatting documentation Martin Kletzander
2015-09-21 9:18 ` Andy Shevchenko
2015-09-21 13:04 ` Martin Kletzander
2015-09-22 18:40 ` Rasmus Villemoes [this message]
2015-09-22 18:48 ` Martin Kletzander
2015-09-23 8:52 ` Andy Shevchenko
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=87si66qovw.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkletzan@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sboyd@codeaurora.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).