From: jgg@ziepe.ca (Jason Gunthorpe)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] tpm: Update MAINTAINERS for Jason Gunthorpe
Date: Wed, 8 Nov 2017 15:24:34 -0700 [thread overview]
Message-ID: <20171108222434.GF7063@ziepe.ca> (raw)
In-Reply-To: <E803B459-CB11-4E23-B3BC-4DEF2A0C40B6@gmx.de>
On Wed, Nov 08, 2017 at 10:27:37AM +0100, Peter Huewe wrote:
> >Updating that file goes out of my territory other than acking the
> >updates.
> Imho not really, since there is no MAINTAINERS maintainer. If you
> feel uncomfortable with adding the changes to MAINTAINERS via your
> tree, please ask James to pull them up - just as Mimi did for her
> linux-integrity update.
Agreed, if you are submitting pull requests then the MAINTAINERS
update for TPM related things should go into your pull request. That
is appropriate..
It isn't necessary for everything to be cc'd everywhere, ultimately it
is your responsibility as the TPM maintainer to accept/reject this
change.
If it was a larger change, like adding/removing a maintainer then a
large audiance would be appropriate, but this is just changing
spelling and the patch was PGP signed ..
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: Update MAINTAINERS for Jason Gunthorpe
Date: Wed, 8 Nov 2017 15:24:34 -0700 [thread overview]
Message-ID: <20171108222434.GF7063@ziepe.ca> (raw)
In-Reply-To: <E803B459-CB11-4E23-B3BC-4DEF2A0C40B6@gmx.de>
On Wed, Nov 08, 2017 at 10:27:37AM +0100, Peter Huewe wrote:
> >Updating that file goes out of my territory other than acking the
> >updates.
> Imho not really, since there is no MAINTAINERS maintainer. If you
> feel uncomfortable with adding the changes to MAINTAINERS via your
> tree, please ask James to pull them up - just as Mimi did for her
> linux-integrity update.
Agreed, if you are submitting pull requests then the MAINTAINERS
update for TPM related things should go into your pull request. That
is appropriate..
It isn't necessary for everything to be cc'd everywhere, ultimately it
is your responsibility as the TPM maintainer to accept/reject this
change.
If it was a larger change, like adding/removing a maintainer then a
large audiance would be appropriate, but this is just changing
spelling and the patch was PGP signed ..
Jason
next prev parent reply other threads:[~2017-11-08 22:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 20:23 [PATCH] tpm: Update MAINTAINERS for Jason Gunthorpe Jason Gunthorpe
2017-11-03 14:28 ` Jarkko Sakkinen
2017-11-03 14:28 ` Jarkko Sakkinen
2017-11-03 16:05 ` Peter Huewe
2017-11-03 16:05 ` Peter Huewe
2017-11-07 15:03 ` Jarkko Sakkinen
2017-11-07 15:03 ` Jarkko Sakkinen
2017-11-08 6:36 ` Jarkko Sakkinen
2017-11-08 6:36 ` Jarkko Sakkinen
2017-11-08 9:27 ` Peter Huewe
2017-11-08 9:27 ` Peter Huewe
2017-11-08 22:24 ` Jason Gunthorpe [this message]
2017-11-08 22:24 ` Jason Gunthorpe
2017-11-14 14:27 ` Jarkko Sakkinen
2017-11-14 14:27 ` Jarkko Sakkinen
2017-11-14 14:25 ` Jarkko Sakkinen
2017-11-14 14:25 ` Jarkko Sakkinen
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=20171108222434.GF7063@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=linux-security-module@vger.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.