linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Grant Likely <grant.likely@arm.com>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation/process: Update ARM contact for embargoed hardware issues
Date: Tue, 5 Apr 2022 15:29:32 +0100	[thread overview]
Message-ID: <YkxSTBBb5Hj1EQPF@arm.com> (raw)
In-Reply-To: <YjyilfhMgbqTo3eL@kroah.com>

On Thu, Mar 24, 2022 at 05:55:49PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Mar 24, 2022 at 03:16:05PM +0000, Catalin Marinas 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>
> > ---
> >  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>
> 
> Nit, no tab is needed.  I missed this on the next line:
> 
> >    AMD		Tom Lendacky <tom.lendacky@amd.com>
> 
> But no need to follow bad decisions :)

I was wondering. There are currently three entries with spaces and the
rest with tabs, so I went with the majority. I'll repost with spaces and
get Grant to ack again without the legal disclaimer.

-- 
Catalin

  reply	other threads:[~2022-04-05 22:40 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
2022-03-24 16:55 ` Greg Kroah-Hartman
2022-04-05 14:29   ` Catalin Marinas [this message]
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=YkxSTBBb5Hj1EQPF@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=grant.likely@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).