[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0d8ee183-7559-99ee-8c83-a902e7215da8@infradead.org>
Date: Thu, 15 Aug 2019 16:10:41 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
security@...nel.org, linux-doc@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Jiri Kosina <jkosina@...e.com>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
Subject: Re: [PATCH] Documentation/admin-guide: Embargoed hardware security
issues
On 8/15/19 3:31 PM, Greg Kroah-Hartman wrote:
> 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?
That's good then. I didn't see the complete sentence.
--
~Randy
Powered by blists - more mailing lists