From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, 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>
Subject: Re: [PATCH] Documentation/admin-guide: Embargoed hardware security issues
Date: Fri, 16 Aug 2019 00:31:47 +0200 [thread overview]
Message-ID: <20190815223147.GA28275@kroah.com> (raw)
In-Reply-To: <e3ae0d66-b9eb-97ba-647a-57f3e2eb4af2@infradead.org>
On Thu, Aug 15, 2019 at 03:12:34PM -0700, Randy Dunlap wrote:
> On 8/15/19 2:20 PM, Greg Kroah-Hartman wrote:
> >>> +The hardware security team will provide a per incident specific encrypted
> >> s/per incident specific/incident-specific/
> > Fixed. And changed /a/ to /an/
>
> eh? still should be /a per incident/
The sentence was changed to:
The hardware security team will provide an incident-specific
encrypted...
is not "an" correct here?
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-15 22:31 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 [this message]
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
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=20190815223147.GA28275@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=jkosina@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=rdunlap@infradead.org \
--cc=security@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 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.