LKML Archive on
help / color / mirror / Atom feed
From: Jerry Snitselaar <>
To: James Morris <>
Cc: Jarkko Sakkinen <>,,,, Peter Huewe <>,
	Jason Gunthorpe <>
Subject: Re: [PATCH] MAINTAINERS: add linux-security-module mailing list to TPM drivers
Date: Wed, 20 Feb 2019 15:39:03 -0700	[thread overview]
Message-ID: <20190220223903.dusft4bbd33hu2qi@cantor> (raw)
In-Reply-To: <>

On Thu Feb 21 19, James Morris wrote:
>On Wed, 20 Feb 2019, Jarkko Sakkinen wrote:
>> > 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
>> > 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.
>Sounds about right, there used to be more security folk on LSM and not as
>many on the TPM list, but the new integrity list works well for TPM now.
>James Morris

Okay. Ignore this patch then.

      reply	other threads:[~2019-02-20 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  3:58 Jerry Snitselaar
2019-02-20  7:04 ` Jarkko Sakkinen
2019-02-20 14:03   ` Jerry Snitselaar
2019-02-20 15:04     ` Jarkko Sakkinen
2019-02-20 20:49       ` James Morris
2019-02-20 22:39         ` Jerry Snitselaar [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190220223903.dusft4bbd33hu2qi@cantor \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] MAINTAINERS: add linux-security-module mailing list to TPM drivers' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).