All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Kees Cook <keescook@chromium.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Randy Dunlap <rdunlap@infradead.org>,
	Andrew Murray <amurray@mpc-data.co.uk>,
	linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] doc: convert printk-formats.txt to rst
Date: Fri, 8 Dec 2017 11:46:27 +1100	[thread overview]
Message-ID: <20171208004627.GW2191@eros> (raw)
In-Reply-To: <CAGXu5j+fFu7_quVm4+q3Npf_iWN5xjy9GzuYCDcxFW9RSyVkPQ@mail.gmail.com>

On Thu, Dec 07, 2017 at 04:19:56PM -0800, Kees Cook wrote:
> On Thu, Dec 7, 2017 at 3:44 PM, Tobin C. Harding <me@tobin.cc> wrote:
> > Cheers Kees. FTR, changes to implement are:
> >
> >  - Fix the capitalization of 'kernel'.
> 
> I don't really have an opinion about which way is right. I personally
> don't capitalize it unless I speak about it as a single thing "The
> Linux Kernel". In this case I just noticed you had mixed usage.
> 
> >  - Add ESCAPE_* flags back into kernel-docs in lib/vsprintf.c
> 
> I actually meant each of the sections. Several of the formats have
> per-item breakdowns that went missing in the new kernel-doc (ESCAPE_*
> was just an example).

Oh dear, you don't like that. This is actually the part of the patch
that I was least sure about doing. I'm happy to revert, can I give you
my thought process for comment?

When the kernel-docs get included into printk-formats.rst it seems
overly verbose to have all the information given twice. And then it
seems odd to bother having the extra descriptions in printk-formats.rst
if _all_ the required information is already in the kernel-docs?

So I guessed that it would be nice for devs to get a bit of a hint at
the specifiers when having lib/vsprintf.c open (and they have the code
too) then if they needed more information going to printk-formats.rst.

Also, since there is more space in printk-fomats.rst the info can be
spaced better and easier to read.

Your thoughts?

thanks,
Tobin.

  reply	other threads:[~2017-12-08  0:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  1:45 [PATCH] doc: convert printk-formats.txt to rst Tobin C. Harding
2017-12-06  7:11 ` Markus Heiser
2017-12-06  7:35   ` Joe Perches
2017-12-06 17:55     ` Randy Dunlap
2017-12-06 18:18 ` Randy Dunlap
2017-12-06 21:16   ` Tobin C. Harding
2017-12-07  0:39     ` Randy Dunlap
2017-12-07  5:25       ` Tobin C. Harding
2017-12-06 22:11   ` Tobin C. Harding
2017-12-06 18:23 ` Jonathan Corbet
2017-12-06 21:30   ` Tobin C. Harding
2017-12-07 22:50 ` Kees Cook
2017-12-07 23:01   ` Jonathan Corbet
2017-12-07 23:50     ` Tobin C. Harding
2017-12-07 23:44   ` Tobin C. Harding
2017-12-08  0:19     ` Kees Cook
2017-12-08  0:46       ` Tobin C. Harding [this message]
2017-12-08 21:06         ` Kees Cook
2017-12-08 21:22           ` Joe Perches
2017-12-09  1:27             ` Tobin C. Harding
2017-12-09  2:18               ` Joe Perches
2017-12-09  6:33                 ` Tobin C. Harding
2017-12-11 18:40                   ` Laura Abbott
2017-12-09 11:48                 ` Dan Carpenter
2017-12-11  0:51                   ` Kees Cook

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=20171208004627.GW2191@eros \
    --to=me@tobin.cc \
    --cc=amurray@mpc-data.co.uk \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.