From: Jonathan Corbet <corbet@lwn.net>
To: Greg KH <greg@kroah.com>
Cc: tglx@linutronix.de, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Process: provide hardware-security list details
Date: Thu, 19 Dec 2019 09:24:21 -0700 [thread overview]
Message-ID: <20191219092421.03e970cb@lwn.net> (raw)
In-Reply-To: <20191209193524.GA1694922@kroah.com>
On Mon, 9 Dec 2019 20:35:24 +0100
Greg KH <greg@kroah.com> wrote:
> On Mon, Dec 09, 2019 at 02:26:11PM -0500, Konstantin Ryabitsev wrote:
> > Fill in "..." stubs with proper links to the mailing lists's encryption
> > keys and service description URLs. Similarly, fix wording to specify
> > that multiple members of Linux Foundation's IT team have access to
> > internal kernel.org infrastructure, and that all of them have similar
> > confidentiality obligations as the IT team director.
> >
> > Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
I've applied this, thanks.
jon
prev parent reply other threads:[~2019-12-19 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 19:26 [PATCH] Process: provide hardware-security list details Konstantin Ryabitsev
2019-12-09 19:35 ` Greg KH
2019-12-19 16:24 ` 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=20191219092421.03e970cb@lwn.net \
--to=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=linux-doc@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).