From: Jonathan Corbet <corbet@lwn.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Documentation: more names to the enforcement statement
Date: Thu, 21 Dec 2017 12:25:45 -0700 [thread overview]
Message-ID: <20171221122545.0c504e0d@lwn.net> (raw)
In-Reply-To: <20171213125255.18891-1-gregkh@linuxfoundation.org>
On Wed, 13 Dec 2017 13:52:52 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> Here are 3 patches for the kernel-enforcement-statement file that came
> in after the file was originally added to the kernel tree.
Applied all three, thanks.
jon
prev parent reply other threads:[~2017-12-21 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 12:52 [PATCH 0/3] Documentation: more names to the enforcement statement Greg Kroah-Hartman
2017-12-13 12:52 ` [PATCH 1/3] Documentation: Add Kees Cook to list of enforcement statement endorsers Greg Kroah-Hartman
2017-12-13 12:52 ` [PATCH 2/3] Documentation: Add Luis R. Rodriguez " Greg Kroah-Hartman
2017-12-13 12:52 ` [PATCH 3/3] Documentation: Add myself to the enforcement statement list Greg Kroah-Hartman
2017-12-21 19:25 ` Jonathan Corbet [this message]
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=20171221122545.0c504e0d@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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