All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
	keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: jarkko.sakkinen@linux.intel.com -> jarkko@kernel.org
Date: Tue, 13 Oct 2020 19:25:24 +0000	[thread overview]
Message-ID: <20201013192524.GA164334@kernel.org> (raw)
In-Reply-To: <dce9442565fc3176ad770788bc1cf76b02080486.camel@perches.com>

On Tue, Oct 13, 2020 at 08:30:38AM -0700, Joe Perches wrote:
> On Tue, 2020-10-13 at 13:46 +0300, Jarkko Sakkinen wrote:
> > Use korg address as the main communications end point. Update the
> > corresponding M-entries.
> 
> Maybe add an equivalent entry to .mailmap?

Ugh, neither has @linux.intel.com. So, I'll insert these two lines:

Jarkko Sakkinen <jarkko@kernel.org>
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

> > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > -M:	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > +M:	Jarkko Sakkinen <jarkko@kernel.org>

Thanks.

/Jarkko

WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
	keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: jarkko.sakkinen@linux.intel.com -> jarkko@kernel.org
Date: Tue, 13 Oct 2020 22:25:24 +0300	[thread overview]
Message-ID: <20201013192524.GA164334@kernel.org> (raw)
In-Reply-To: <dce9442565fc3176ad770788bc1cf76b02080486.camel@perches.com>

On Tue, Oct 13, 2020 at 08:30:38AM -0700, Joe Perches wrote:
> On Tue, 2020-10-13 at 13:46 +0300, Jarkko Sakkinen wrote:
> > Use korg address as the main communications end point. Update the
> > corresponding M-entries.
> 
> Maybe add an equivalent entry to .mailmap?

Ugh, neither has @linux.intel.com. So, I'll insert these two lines:

Jarkko Sakkinen <jarkko@kernel.org>
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

> > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > -M:	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > +M:	Jarkko Sakkinen <jarkko@kernel.org>

Thanks.

/Jarkko

  reply	other threads:[~2020-10-13 19:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 10:46 [PATCH] MAINTAINERS: jarkko.sakkinen@linux.intel.com -> jarkko@kernel.org Jarkko Sakkinen
2020-10-13 10:46 ` Jarkko Sakkinen
2020-10-13 15:30 ` Joe Perches
2020-10-13 15:30   ` Joe Perches
2020-10-13 19:25   ` Jarkko Sakkinen [this message]
2020-10-13 19:25     ` Jarkko Sakkinen
2020-10-13 19:36     ` Joe Perches
2020-10-13 19:36       ` Joe Perches

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=20201013192524.GA164334@kernel.org \
    --to=jarkko@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=joe@perches.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=robh@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.