public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Tobin C. Harding" <me@tobin.cc>, Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kees Cook <keescook@chromium.org>,
	Alexander Popov <alex.popov@linux.com>,
	kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v2 0/3] doc: update printk documentation
Date: Sun, 17 Dec 2017 14:34:25 -0800	[thread overview]
Message-ID: <1513550065.31581.39.camel@perches.com> (raw)
In-Reply-To: <1513549807-20287-1-git-send-email-me@tobin.cc>

On Mon, 2017-12-18 at 09:30 +1100, Tobin C. Harding wrote:
> This set converts printk-formats.txt -> core-api/printk-formats.rst
> 
> We also update the documentation around printing kernel addresses.

Please also update the comment in lib/vsprintf.c

 * ** Please update also Documentation/printk-formats.txt when making changes **

> I'd like to get it _realy_ correct so that future

sp: realy->really

  parent reply	other threads:[~2017-12-17 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17 22:30 [PATCH v2 0/3] doc: update printk documentation Tobin C. Harding
2017-12-17 22:30 ` [PATCH v2 1/3] doc: convert printk-formats.txt to rst Tobin C. Harding
2017-12-17 22:30 ` [PATCH v2 2/3] doc: update kpt_restrict documentation Tobin C. Harding
2017-12-18  2:48   ` Randy Dunlap
2017-12-17 22:30 ` [PATCH v2 3/3] doc: add documentation on printing kernel addresses Tobin C. Harding
2017-12-17 22:34 ` Joe Perches [this message]
2017-12-17 23:56   ` [PATCH v2 0/3] doc: update printk documentation Tobin C. Harding

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=1513550065.31581.39.camel@perches.com \
    --to=joe@perches.com \
    --cc=alex.popov@linux.com \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox