From: peterhuewe@gmx.de (Peter Huewe) To: linux-security-module@vger.kernel.org Subject: [PATCH] tpm: Update MAINTAINERS for Jason Gunthorpe Date: Fri, 03 Nov 2017 17:05:49 +0100 [thread overview] Message-ID: <0812DDC3-187D-4F29-BFB5-9A4F509CA376@gmx.de> (raw) In-Reply-To: <20171103142841.2nphkjojzamrdezm@linux.intel.com> Am 3. November 2017 15:28:41 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>: >On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: >> My email address for open source work is moving to this new permanent >> personal address. >> >> Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> >> --- >> MAINTAINERS | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 6671f375f7fcdd..b79eb071475ffc 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER >> M: Peter Huewe <peterhuewe@gmx.de> >> M: Marcel Selhorst <tpmdd@selhorst.net> >> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> >> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> >> +R: Jason Gunthorpe <jgg@ziepe.ca> >> W: http://tpmdd.sourceforge.net >> L: tpmdd-devel at lists.sourceforge.net (moderated for non-subscribers) >> Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ >> -- >> 2.7.4 >> > >Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > >Should these updates go to my tree? I posted previous update to >linux-kernel at vger.kernel.org. Which equals /dev/null for most cases. Why shouldn'tit go through your tree? It's a maintainers update for your subsystem - and you did it in the past when modifying the urls. >/Jarkko -- Sent from my mobile -- 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: Peter Huewe <peterhuewe@gmx.de> To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>, Jason Gunthorpe <jgg@ziepe.ca> Cc: linux-security-module@vger.kernel.org, linux-integrity@vger.kernel.org Subject: Re: [PATCH] tpm: Update MAINTAINERS for Jason Gunthorpe Date: Fri, 03 Nov 2017 17:05:49 +0100 [thread overview] Message-ID: <0812DDC3-187D-4F29-BFB5-9A4F509CA376@gmx.de> (raw) In-Reply-To: <20171103142841.2nphkjojzamrdezm@linux.intel.com> Am 3. November 2017 15:28:41 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>: >On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: >> My email address for open source work is moving to this new permanent >> personal address. >> >> Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> >> --- >> MAINTAINERS | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 6671f375f7fcdd..b79eb071475ffc 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER >> M: Peter Huewe <peterhuewe@gmx.de> >> M: Marcel Selhorst <tpmdd@selhorst.net> >> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> >> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> >> +R: Jason Gunthorpe <jgg@ziepe.ca> >> W: http://tpmdd.sourceforge.net >> L: tpmdd-devel@lists.sourceforge.net (moderated for non-subscribers) >> Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ >> -- >> 2.7.4 >> > >Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > >Should these updates go to my tree? I posted previous update to >linux-kernel@vger.kernel.org. Which equals /dev/null for most cases. Why shouldn'tit go through your tree? It's a maintainers update for your subsystem - and you did it in the past when modifying the urls. >/Jarkko -- Sent from my mobile
next prev parent reply other threads:[~2017-11-03 16:05 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 [this message] 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 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=0812DDC3-187D-4F29-BFB5-9A4F509CA376@gmx.de \ --to=peterhuewe@gmx.de \ --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: linkBe 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.