All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Sasha Levin <sashal@kernel.org>
Cc: tglx@linutronix.de, gregkh@linuxfoundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	konrad.wilk@oracle.com, jkosina@suse.cz, tyhicks@canonical.com,
	linux-kernel@microsoft.com,
	Sasha Levin <alexander.levin@microsoft.com>
Subject: Re: [PATCH] Documentation/process/embargoed-hardware-issues: Microsoft ambassador
Date: Fri, 6 Sep 2019 08:57:28 -0600	[thread overview]
Message-ID: <20190906085728.15af96c3@lwn.net> (raw)
In-Reply-To: <20190906095852.23568-1-sashal@kernel.org>

On Fri,  6 Sep 2019 05:58:52 -0400
Sasha Levin <sashal@kernel.org> wrote:

> Add Sasha Levin as Microsoft's process ambassador.
> 
> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
> Signed-off-by: Sasha Levin <sashal@kernel.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@kernel.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?

Thanks,

jon

  reply	other threads:[~2019-09-06 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  9:58 [PATCH] Documentation/process/embargoed-hardware-issues: Microsoft ambassador Sasha Levin
2019-09-06 14:57 ` Jonathan Corbet [this message]
2019-09-06 16:13   ` Greg KH

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=20190906085728.15af96c3@lwn.net \
    --to=corbet@lwn.net \
    --cc=alexander.levin@microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tyhicks@canonical.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.