linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] tpm: Update MAINTAINERS for Jason Gunthorpe
Date: Wed, 8 Nov 2017 08:36:40 +0200	[thread overview]
Message-ID: <20171108063640.kxwag6fzguetpjnf@linux.intel.com> (raw)
In-Reply-To: <20171107150356.uln3lks64zt5oxjv@linux.intel.com>

On Tue, Nov 07, 2017 at 05:03:56PM +0200, Jarkko Sakkinen wrote:
> On Fri, Nov 03, 2017 at 05:05:49PM +0100, Peter Huewe wrote:
> > 
> > 
> > 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
> 
> I applied two patches to my tree.
> 
> /Jarkko

NAK

linux-kernel at vger.kernel.org is missing *completely*. It should be at
minimum in the CC field.

My previous update did not go through my tree. I misread your original
response to say that I should put also URL update to my tree. I did.
It resulted a merge conflict.

Updating that file goes out of my territory other than acking the
updates. Now that linux-kernel is missing this completely unacceptable.

/Jarkko
--
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

  reply	other threads:[~2017-11-08  6:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171031202357.GA1030@ziepe.ca>
2017-11-03 14:28 ` [PATCH] tpm: Update MAINTAINERS for Jason Gunthorpe Jarkko Sakkinen
2017-11-03 16:05   ` Peter Huewe
2017-11-07 15:03     ` Jarkko Sakkinen
2017-11-08  6:36       ` Jarkko Sakkinen [this message]
2017-11-08  9:27         ` Peter Huewe
2017-11-08 22:24           ` Jason Gunthorpe
2017-11-14 14:27             ` 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=20171108063640.kxwag6fzguetpjnf@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --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 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).