linux-kernel - Re: [PATCH] Documentation/process: Update ARM contact for embargoed hardware issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 5 Apr 2022 15:29:32 +0100
From:   Catalin Marinas <catalin.marinas@....com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Grant Likely <grant.likely@....com>,
        Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH] Documentation/process: Update ARM contact for embargoed
 hardware issues

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@....com>
> > Cc: Grant Likely <grant.likely@....com>
> > Cc: Jonathan Corbet <corbet@....net>
> > Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.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@....com>
> > +  ARM		Catalin Marinas <catalin.marinas@....com>
> 
> Nit, no tab is needed.  I missed this on the next line:
> 
> >    AMD		Tom Lendacky <tom.lendacky@....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