From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 1/3] Documentation: Add Kees Cook to list of enforcement statement endorsers
Date: Wed, 13 Dec 2017 13:52:53 +0100 [thread overview]
Message-ID: <20171213125255.18891-2-gregkh@linuxfoundation.org> (raw)
In-Reply-To: <20171213125255.18891-1-gregkh@linuxfoundation.org>
From: Kees Cook <keescook@chromium.org>
Add my name to the list.
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
Documentation/process/kernel-enforcement-statement.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/process/kernel-enforcement-statement.rst b/Documentation/process/kernel-enforcement-statement.rst
index bfa6a78103d8..99a9135a965c 100644
--- a/Documentation/process/kernel-enforcement-statement.rst
+++ b/Documentation/process/kernel-enforcement-statement.rst
@@ -68,6 +68,7 @@ we might work for today, have in the past, or will in the future.
- Paul Burton
- Javier Martinez Canillas
- Rob Clark
+ - Kees Cook (Google)
- Jonathan Corbet
- Dennis Dalessandro
- Vivien Didelot (Savoir-faire Linux)
--
2.15.1
next prev parent reply other threads:[~2017-12-13 12:53 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 ` Greg Kroah-Hartman [this message]
2017-12-13 12:52 ` [PATCH 2/3] Documentation: Add Luis R. Rodriguez to list of enforcement statement endorsers 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 ` [PATCH 0/3] Documentation: more names to the enforcement statement Jonathan Corbet
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=20171213125255.18891-2-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=keescook@chromium.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 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.