[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7da72334-f3ea-fe73-b4b4-bec97ae15946@amd.com>
Date: Fri, 29 Jul 2022 07:59:42 -0500
From: Tom Lendacky <thomas.lendacky@....com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org
Cc: linux-doc@...r.kernel.org,
linux-doc-tw-discuss@...ts.sourceforge.net,
Jonathan Corbet <corbet@....net>, Alex Shi <alexs@...nel.org>,
Yanteng Si <siyanteng@...ngson.cn>,
Hu Haowen <src.res@...il.cn>
Subject: Re: [PATCH] docs: embargoed-hardware-issues: remove bouncing AMD
contact info
On 7/29/22 05:20, Greg Kroah-Hartman wrote:
> On Fri, Jul 29, 2022 at 12:07:45PM +0200, Greg Kroah-Hartman wrote:
>> The current AMD contact info in the embargoed-hardware-issues.rst file
>> is bouncing as an invalid address, so remove it from the documentation.
>>
>> At this point in time, the kernel community has no way to contact AMD
>> for any hardware-specific problems. Hopefully they can resolve this
>> issue soon, or maybe they just don't have any hardware bugs and do not
>> need to worry about this.
>>
>> Cc: Jonathan Corbet <corbet@....net>
>> Cc: Alex Shi <alexs@...nel.org>
>> Cc: Yanteng Si <siyanteng@...ngson.cn>
>> Cc: Hu Haowen <src.res@...il.cn>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> ---
>> Documentation/process/embargoed-hardware-issues.rst | 2 +-
>> .../translations/zh_CN/process/embargoed-hardware-issues.rst | 2 +-
>> .../translations/zh_TW/process/embargoed-hardware-issues.rst | 2 +-
>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
>> index 95999302d279..a8c38e1c40dc 100644
>> --- a/Documentation/process/embargoed-hardware-issues.rst
>> +++ b/Documentation/process/embargoed-hardware-issues.rst
>> @@ -244,7 +244,7 @@ disclosure of a particular issue, unless requested by a response team or by
>> an involved disclosed party. The current ambassadors list:
>>
>> ============= ========================================================
>> - AMD Tom Lendacky <tom.lendacky@....com>
>> + AMD
>
> Wait, Tom, is this just the wrong email address for you? And the one
> above I used in the To: the correct one?
Wow, yes, I can't believe I made that mistake and haven't noticed it! You
are correct, it should be thomas.lendacky@....com.
Thanks,
Tom
>
> confused,
>
> greg k-h
Powered by blists - more mailing lists