From: Randy Dunlap <rdunlap@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Cc: security@kernel.org, linux-doc@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Kosina <jkosina@suse.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Laura Abbott <labbott@redhat.com>,
Ben Hutchings <ben@decadent.org.uk>,
Tyler Hicks <tyhicks@canonical.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH v2] Documentation/admin-guide: Embargoed hardware security issues
Date: Thu, 15 Aug 2019 15:15:11 -0700 [thread overview]
Message-ID: <635f5f3d-dc1e-90a0-8d85-d26a786bb910@infradead.org> (raw)
In-Reply-To: <20190815212505.GC12041@kroah.com>
On 8/15/19 2:25 PM, Greg Kroah-Hartman wrote:
> v2: updated list of people with document from Jiri as I had the old one
> grammer tweaks based on Jon's review
> moved document to Documentation/process/
If you get to do a v3, you can change the $Subject also.
--
~Randy
next prev parent reply other threads:[~2019-08-15 22:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 13:01 [PATCH] Documentation/admin-guide: Embargoed hardware security issues Greg Kroah-Hartman
2019-07-25 21:13 ` Jonathan Corbet
2019-07-26 14:47 ` Thomas Gleixner
2019-08-15 21:20 ` Greg Kroah-Hartman
2019-08-15 22:12 ` Randy Dunlap
2019-08-15 22:31 ` Greg Kroah-Hartman
2019-08-15 23:10 ` Randy Dunlap
2019-08-02 4:49 ` Willy Tarreau
2019-08-02 6:57 ` Greg Kroah-Hartman
2019-08-02 9:24 ` Willy Tarreau
2019-08-04 0:17 ` Jiri Kosina
2019-08-04 0:21 ` Jiri Kosina
2019-08-05 14:40 ` Eric W. Biederman
2019-08-05 14:59 ` Greg Kroah-Hartman
2019-08-05 15:12 ` Greg Kroah-Hartman
2019-08-15 21:04 ` Greg Kroah-Hartman
2019-08-15 21:25 ` [PATCH v2] " Greg Kroah-Hartman
2019-08-15 22:15 ` Randy Dunlap [this message]
2019-08-15 22:31 ` Greg Kroah-Hartman
2019-08-20 14:58 ` Josh Poimboeuf
2019-08-20 16:58 ` Greg Kroah-Hartman
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=635f5f3d-dc1e-90a0-8d85-d26a786bb910@infradead.org \
--to=rdunlap@infradead.org \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.com \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=labbott@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=security@kernel.org \
--cc=tglx@linutronix.de \
--cc=tyhicks@canonical.com \
/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).