From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: jmorris@namei.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] MAINTAINERS: add linux-security-module mailing list to TPM drivers
Date: Wed, 20 Feb 2019 17:04:45 +0200 [thread overview]
Message-ID: <20190220150445.GA4794@linux.intel.com> (raw)
In-Reply-To: <20190220140357.5vbepgmexso3jc6d@cantor>
On Wed, Feb 20, 2019 at 07:03:57AM -0700, Jerry Snitselaar wrote:
> On Wed Feb 20 19, Jarkko Sakkinen wrote:
> > On Tue, Feb 19, 2019 at 08:58:46PM -0700, Jerry Snitselaar wrote:
> > > I've seen requests to add linux-security-module to tpm patch
> > > submissions a couple of times recently, so just add the list
> > > to MAINTAINERS so get_maintainers.pl will mention it.
> > >
> > > Cc: Peter Huewe <peterhuewe@gmx.de>
> > > Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > > Cc: Jason Gunthorpe <jgg@ziepe.ca>
> > > Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
> >
> > I guess James should say something about this.
> >
> > /Jarkko
>
> Sorry, I meant to add James as well.
>
> Maybe this isn't needed. Do you only want certain patches
> being cc'd to linux-security-module? Looking back at
> recent patches, it looked like it was a general request.
> If it is, I'll be more likely to remember if get_maintainers.pl
> brings it up. :)
I'm all open here. Not sure which practices apply to IMA. I kind of tend
to dilate to question does it make sense to CC to LSM for two reasons:
1. I think the original reason was that tpmdd mailing list was small.
Now with the new linux-integrity mailing list up and running there is
more eyes looking at the code. And more importantly the people are
subscribed who use TPM for something, like IMA developers.
2. I don't remember ever reading within the time that I've been
maintaining even a single comment from anyone that works with LSM's. The
value of CC'ing there is not very significant, which means that most of
the time the TPM traffic is just noise on that list.
/Jarkko
next prev parent reply other threads:[~2019-02-20 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 3:58 [PATCH] MAINTAINERS: add linux-security-module mailing list to TPM drivers Jerry Snitselaar
2019-02-20 7:04 ` Jarkko Sakkinen
2019-02-20 14:03 ` Jerry Snitselaar
2019-02-20 15:04 ` Jarkko Sakkinen [this message]
2019-02-20 20:49 ` James Morris
2019-02-20 22:39 ` Jerry Snitselaar
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=20190220150445.GA4794@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).