Re: [PATCH] docs: embargoed-hardware-issues: remove bouncing AMD contact info
From: Greg Kroah-Hartman
Date: Fri Jul 29 2022 - 09:40:27 EST
On Fri, Jul 29, 2022 at 07:59:42AM -0500, Tom Lendacky wrote:
> 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@xxxxxxx>
> > > Cc: Alex Shi <alexs@xxxxxxxxxx>
> > > Cc: Yanteng Si <siyanteng@xxxxxxxxxxx>
> > > Cc: Hu Haowen <src.res@xxxxxxxx>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> > > ---
> > > 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@xxxxxxx>
> > > + 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@xxxxxxx.
Ok, let me go fix this up and change the address in the files and redo
this patch.
thanks,
greg k-h