From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Grant Likely <Grant.Likely@arm.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation/process: Update ARM contact for embargoed hardware issues
Date: Thu, 24 Mar 2022 17:55:11 +0100 [thread overview]
Message-ID: <YjyibzHcFamjx0JD@kroah.com> (raw)
In-Reply-To: <F5B89578-5AEE-4C29-B146-B84265FD2B4E@arm.com>
On Thu, Mar 24, 2022 at 03:39:09PM +0000, Grant Likely wrote:
>
> > On 24 Mar 2022, at 15:16, Catalin Marinas <Catalin.Marinas@arm.com> wrote:
> >
> > With Grant taking a prominent role in Linaro, I will take over as the
> > process ambassador for ARM w.r.t. embargoed hardware issues.
> >
> > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Grant Likely <grant.likely@arm.com>
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Acked-by: Grant Likely <grant.likely@arm.com>
>
> > ---
> > Documentation/process/embargoed-hardware-issues.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
> > index 6f8f36e10e8b..41a2afaaea75 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:
> >
> > ============= ========================================================
> > - ARM Grant Likely <grant.likely@arm.com>
> > + ARM Catalin Marinas <catalin.marinas@arm.com>
> > AMD Tom Lendacky <tom.lendacky@amd.com>
> > IBM Z Christian Borntraeger <borntraeger@de.ibm.com>
> > IBM Power Anton Blanchard <anton@linux.ibm.com>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Response is now dropped :(
Grant, you know better....
next prev parent reply other threads:[~2022-03-24 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 15:16 [PATCH] Documentation/process: Update ARM contact for embargoed hardware issues Catalin Marinas
2022-03-24 15:39 ` Grant Likely
2022-03-24 16:55 ` Greg Kroah-Hartman [this message]
2022-03-24 16:55 ` Greg Kroah-Hartman
2022-04-05 14:29 ` Catalin Marinas
2022-04-05 16:19 ` Jonathan Corbet
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=YjyibzHcFamjx0JD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Catalin.Marinas@arm.com \
--cc=Grant.Likely@arm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox