From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org, kys@microsoft.com,
jamorris@microsoft.com
Subject: Re: [PATCH] Documentation/process: Change Microsoft contact for embargoed hardware issues
Date: Wed, 5 Feb 2020 21:47:16 +0000 [thread overview]
Message-ID: <20200205214716.GA1468203@kroah.com> (raw)
In-Reply-To: <20200205213621.31474-1-sashal@kernel.org>
On Wed, Feb 05, 2020 at 04:36:21PM -0500, Sasha Levin wrote:
> Remove Sasha Levin as the Microsoft contact. A new contact will be
> assigned by Microsoft.
>
> 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 33edae654599..a6f4f6e5c78b 100644
> --- a/Documentation/process/embargoed-hardware-issues.rst
> +++ b/Documentation/process/embargoed-hardware-issues.rst
> @@ -250,7 +250,7 @@ an involved disclosed party. The current ambassadors list:
> Intel Tony Luck <tony.luck@intel.com>
> Qualcomm Trilok Soni <tsoni@codeaurora.org>
>
> - Microsoft Sasha Levin <sashal@kernel.org>
> + Microsoft
That's fine, but when will that contact "be assigned"? I'd rather not
go without one at all for no good reason other than "people need to
figure their stuff out" :)
thanks,
greg k-h
next prev parent reply other threads:[~2020-02-05 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 21:36 [PATCH] Documentation/process: Change Microsoft contact for embargoed hardware issues Sasha Levin
2020-02-05 21:47 ` Greg KH [this message]
2020-02-05 21:54 ` James Morris
2020-02-05 22:12 ` Greg KH
2020-02-05 22:22 ` James Morris
2020-02-05 22:46 ` Greg KH
2020-02-05 22:01 ` Sasha Levin
2020-02-05 23:08 James Morris
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=20200205214716.GA1468203@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=jamorris@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@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 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.