All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Kees Cook <keescook@chromium.org>,
	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 10:50:35 +1100	[thread overview]
Message-ID: <20171207235035.GU2191@eros> (raw)
In-Reply-To: <20171207160146.608264e1@lwn.net>

On Thu, Dec 07, 2017 at 04:01:46PM -0700, Jonathan Corbet wrote:
> On Thu, 7 Dec 2017 14:50:42 -0800
> Kees Cook <keescook@chromium.org> wrote:
> 
> > > +These guides contain general information useful when writing kernel code.
> > > +
> > > +.. toctree::
> > > +   :maxdepth: 1
> > > +
> > > +   printk-formats  
> > 
> > I actually think this belongs in the kernel core API documentation
> > list (Documentation/core-api/index.rst). I defer to Jon's opinion,
> > though.
> 
> That's my opinion too, and what I had suggested in response to the 
> previous version.  I suspect the pernicious influence of wombats! :)

Steady on! Don't overuse it, you'll hurt my feelings :) Just kidding. I
believe I got this right in the current version. If you are getting
confused trying to follow these patches just try and follow the
discussion my previous effort when hashing %p

I'll let it settle a bit and re-spin after the weekend.

thanks,
Tobin.

  reply	other threads:[~2017-12-07 23:50 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 [this message]
2017-12-07 23:44   ` Tobin C. Harding
2017-12-08  0:19     ` Kees Cook
2017-12-08  0:46       ` Tobin C. Harding
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=20171207235035.GU2191@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.