From: Luis Chamberlain <mcgrof@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Konstantin Ryabitsev <mricon@kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Anton Blanchard <anton@linux.ibm.com>,
Trilok Soni <tsoni@codeaurora.org>,
James Morris <jamorris@linux.microsoft.com>,
corbet@lwn.net, javier.gonz@samsung.com,
linux-doc@vger.kernel.org, a.manzanares@samsung.com,
dave@stgolabs.net, darren@os.amperecomputing.com,
ndesaulniers@google.com, gost.dev@samsung.com,
linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof.c@samsung.com>
Subject: Re: [PATCH] docs: embargoed-hardware-issues: add embargoed HW contact for Samsung
Date: Tue, 24 Jan 2023 08:22:45 -0800 [thread overview]
Message-ID: <Y9AF1UV/ow7eP92L@bombadil.infradead.org> (raw)
In-Reply-To: <Y89qrid7YOsIFbD6@kroah.com>
On Tue, Jan 24, 2023 at 06:20:46AM +0100, Greg KH wrote:
> On Tue, Jan 24, 2023 at 02:39:53AM +0000, Matthew Wilcox wrote:
> > On Mon, Jan 23, 2023 at 01:48:03PM -0800, Luis Chamberlain wrote:
> > > > > @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list:
> > > > > IBM Z Christian Borntraeger <borntraeger@de.ibm.com>
> > > > > Intel Tony Luck <tony.luck@intel.com>
> > > > > Qualcomm Trilok Soni <tsoni@codeaurora.org>
> > > > > + Samsung Javier González <javier.gonz@samsung.com>
> > >
> > > I'll send a fix on v2.
> > >
> > > BTW while at it, it got me wondering, since most of the emails on
> > > this hw embargo page are not required to have kernel.org accounts
> >
> > This isn't the list of hw embargo people. This is the list of
> > "ambassadors" who can help people work through the security disclosure
> > process. My impression is that it's to tell me that I should contact
> > Konrad, since he also works at Oracle, to help me through the process.
> > It's not for people outside Oracle to contact.
> >
> > If I have the wrong impression of that list, perhaps the description
> > could be clarified.
>
> That is correct, but it is primarily a list that I use when needing to
> contact companies about potential issues in their hardware.
That is the impression I gathered.
> For that I
> don't need a GPG key, that's only required if they need to get added to
> a secure mailing list, and at that point I can have a key sent to me, it
> does not have to be in our kernel.org keyring at all (and list
> participants usually are not there.)
That might be useful to explain in the documentation.
> So there's no need for any of these addresses to be part of the kernel
> gpg ring of trust for any of their activities.
Sounds good.
Luis
next prev parent reply other threads:[~2023-01-24 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 18:39 Luis Chamberlain
2023-01-23 18:54 ` Greg KH
2023-01-23 21:48 ` Luis Chamberlain
2023-01-24 2:39 ` Matthew Wilcox
2023-01-24 5:20 ` Greg KH
2023-01-24 16:22 ` Luis Chamberlain [this message]
2023-01-24 16:38 ` Greg KH
2023-01-24 11:41 ` Catalin Marinas
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=Y9AF1UV/ow7eP92L@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=a.manzanares@samsung.com \
--cc=anton@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=darren@os.amperecomputing.com \
--cc=dave@stgolabs.net \
--cc=gost.dev@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jamorris@linux.microsoft.com \
--cc=javier.gonz@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof.c@samsung.com \
--cc=mricon@kernel.org \
--cc=ndesaulniers@google.com \
--cc=thomas.lendacky@amd.com \
--cc=tsoni@codeaurora.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®