mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Greg KH <gregkh@linuxfoundation.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>
Cc: corbet@lwn.net, javier.gonz@samsung.com,
	linux-doc@vger.kernel.org, a.manzanares@samsung.com,
	dave@stgolabs.net, darren@os.amperecomputing.com,
	catalin.marinas@arm.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: Mon, 23 Jan 2023 13:48:03 -0800	[thread overview]
Message-ID: <Y88Ak8K5mD7tFItG@bombadil.infradead.org> (raw)
In-Reply-To: <Y87X6tFlevIebcc6@kroah.com>

On Mon, Jan 23, 2023 at 07:54:34PM +0100, Greg KH wrote:
> On Mon, Jan 23, 2023 at 10:39:26AM -0800, Luis Chamberlain wrote:
> > After discussions internally at the company, Javier has been volunteered
> > and is willing to be the embargoed hardware contact for Samsung.
> > 
> > Cc: Javier González <javier.gonz@samsung.com>
> > Signed-off-by: Luis Chamberlain <mcgrof.c@samsung.com>
> > ---
> >  Documentation/process/embargoed-hardware-issues.rst | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
> > index b6b4481e2474..fbb754253cf7 100644
> > --- a/Documentation/process/embargoed-hardware-issues.rst
> > +++ b/Documentation/process/embargoed-hardware-issues.rst
> > @@ -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>
> 
> No tab?  :(

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
not all of the folks on that page have a PGP key on the pgpkeys git
tree [0]. Today we constrain kernel.org accounts to folks that send
pull requests to Linus. Not all folks on the embargo list need to also
be active kernel developers. Given the issues reported before by Konstantin
on PGP keyservers we rely on our own git tree for keys we wish to get access
to in our community. The below email addresses do not have any PGP
key associated on the pgpkeys tree as of this day.

  * 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

So it occurs to me to perhaps modify pgpg keys documentation to welcome
community related keys to at least include folks like the above for the
hw embargo emails should communication via PGP be required. Thoughts?

[0] https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git

  Luis

  reply	other threads:[~2023-01-23 21:48 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 [this message]
2023-01-24  2:39     ` Matthew Wilcox
2023-01-24  5:20       ` Greg KH
2023-01-24 16:22         ` Luis Chamberlain
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=Y88Ak8K5mD7tFItG@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 \
    /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®