All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Joe Perches <joe@perches.com>
Cc: "Tobin C. Harding" <me@tobin.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 v4 0/3] doc: update printk documentation
Date: Thu, 21 Dec 2017 12:34:47 -0700	[thread overview]
Message-ID: <20171221123447.3727a03b@lwn.net> (raw)
In-Reply-To: <1513884657.4599.16.camel@perches.com>

On Thu, 21 Dec 2017 11:30:57 -0800
Joe Perches <joe@perches.com> wrote:

> > >  - There's a dangling reference to printk-formats.txt in lib/vsprintf.c  
> >    that we'll want to fix up.  
> 
> patch 1/3 updates that reference.

It updates one of them - there were two, one of which remains.  I'll just
toss in a patch to do that one too.

jon

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Joe Perches <joe@perches.com>
Cc: "Tobin C. Harding" <me@tobin.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: [kernel-hardening] Re: [PATCH v4 0/3] doc: update printk documentation
Date: Thu, 21 Dec 2017 12:34:47 -0700	[thread overview]
Message-ID: <20171221123447.3727a03b@lwn.net> (raw)
In-Reply-To: <1513884657.4599.16.camel@perches.com>

On Thu, 21 Dec 2017 11:30:57 -0800
Joe Perches <joe@perches.com> wrote:

> > >  - There's a dangling reference to printk-formats.txt in lib/vsprintf.c  
> >    that we'll want to fix up.  
> 
> patch 1/3 updates that reference.

It updates one of them - there were two, one of which remains.  I'll just
toss in a patch to do that one too.

jon

  reply	other threads:[~2017-12-21 19:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 21:17 [PATCH v4 0/3] doc: update printk documentation Tobin C. Harding
2017-12-19 21:17 ` [kernel-hardening] " Tobin C. Harding
2017-12-19 21:17 ` [PATCH v4 1/3] doc: convert printk-formats.txt to rst Tobin C. Harding
2017-12-19 21:17   ` [kernel-hardening] " Tobin C. Harding
2017-12-19 21:17 ` [PATCH v4 2/3] doc: update kptr_restrict documentation Tobin C. Harding
2017-12-19 21:17   ` [kernel-hardening] " Tobin C. Harding
2017-12-19 21:17 ` [PATCH v4 3/3] doc: add documentation on printing kernel addresses Tobin C. Harding
2017-12-19 21:17   ` [kernel-hardening] " Tobin C. Harding
2017-12-21 19:21 ` [PATCH v4 0/3] doc: update printk documentation Jonathan Corbet
2017-12-21 19:21   ` [kernel-hardening] " Jonathan Corbet
2017-12-21 19:26   ` Randy Dunlap
2017-12-21 19:26     ` [kernel-hardening] " Randy Dunlap
2017-12-21 21:59     ` Tobin C. Harding
2017-12-21 21:59       ` [kernel-hardening] " Tobin C. Harding
2017-12-21 19:30   ` Joe Perches
2017-12-21 19:30     ` [kernel-hardening] " Joe Perches
2017-12-21 19:34     ` Jonathan Corbet [this message]
2017-12-21 19:34       ` Jonathan Corbet
2017-12-21 22:04   ` Tobin C. Harding
2017-12-21 22:04     ` [kernel-hardening] " 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=20171221123447.3727a03b@lwn.net \
    --to=corbet@lwn.net \
    --cc=alex.popov@linux.com \
    --cc=joe@perches.com \
    --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 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.