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] [day] [month] [year] [list]
Message-ID: <20190906161333.GB10547@kroah.com>
Date:   Fri, 6 Sep 2019 18:13:33 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     Sasha Levin <sashal@...nel.org>, tglx@...utronix.de,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        konrad.wilk@...cle.com, jkosina@...e.cz, tyhicks@...onical.com,
        linux-kernel@...rosoft.com,
        Sasha Levin <alexander.levin@...rosoft.com>
Subject: Re: [PATCH] Documentation/process/embargoed-hardware-issues:
 Microsoft ambassador

On Fri, Sep 06, 2019 at 08:57:28AM -0600, Jonathan Corbet wrote:
> On Fri,  6 Sep 2019 05:58:52 -0400
> Sasha Levin <sashal@...nel.org> wrote:
> 
> > Add Sasha Levin as Microsoft's process ambassador.
> > 
> > Signed-off-by: Sasha Levin <alexander.levin@...rosoft.com>
> > Signed-off-by: Sasha Levin <sashal@...nel.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 d37cbc502936d..9a92ccdbce74e 100644
> > --- a/Documentation/process/embargoed-hardware-issues.rst
> > +++ b/Documentation/process/embargoed-hardware-issues.rst
> > @@ -219,7 +219,7 @@ an involved disclosed party. The current ambassadors list:
> >    Intel
> >    Qualcomm
> >  
> > -  Microsoft
> > +  Microsoft	Sasha Levin <sashal@...nel.org>
> >    VMware
> >    XEN
> 
> This document went upstream via Greg's tree, so updates are awkward for
> me to apply without having to explain a late backmerge to Linus.  I can
> hold them until after the merge window, unless you (Greg) would like to
> take them sooner?

I already have 3 of these queued up in my tree to go to Linus in the
next few days, so no need to worry about them.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ