All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-doc-tw-discuss@lists.sourceforge.net,
	Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <siyanteng@loongson.cn>, Hu Haowen <src.res@email.cn>
Subject: Re: [PATCH] docs: embargoed-hardware-issues: remove bouncing AMD contact info
Date: Fri, 29 Jul 2022 15:40:16 +0200	[thread overview]
Message-ID: <YuPjQF11kf+8JYxv@kroah.com> (raw)
In-Reply-To: <7da72334-f3ea-fe73-b4b4-bec97ae15946@amd.com>

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@lwn.net>
> > > Cc: Alex Shi <alexs@kernel.org>
> > > Cc: Yanteng Si <siyanteng@loongson.cn>
> > > Cc: Hu Haowen <src.res@email.cn>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.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@amd.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@amd.com.

Ok, let me go fix this up and change the address in the files and redo
this patch.

thanks,

greg k-h

      reply	other threads:[~2022-07-29 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 10:07 [PATCH] docs: embargoed-hardware-issues: remove bouncing AMD contact info Greg Kroah-Hartman
2022-07-29 10:20 ` Greg Kroah-Hartman
2022-07-29 12:59   ` Tom Lendacky
2022-07-29 13:40     ` Greg Kroah-Hartman [this message]

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=YuPjQF11kf+8JYxv@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc-tw-discuss@lists.sourceforge.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siyanteng@loongson.cn \
    --cc=src.res@email.cn \
    --cc=thomas.lendacky@amd.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 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.