From: Catalin Marinas <catalin.marinas@arm.com>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: torvalds@linux-foundation.org, will.deacon@arm.com,
punitagrawal@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mailmap: Update email for Punit Agrawal
Date: Mon, 5 Nov 2018 10:02:02 +0000 [thread overview]
Message-ID: <20181105100202.GA23421@arrakis.emea.arm.com> (raw)
In-Reply-To: <20181102165751.17948-1-punit.agrawal@arm.com>
On Fri, Nov 02, 2018 at 04:57:52PM +0000, Punit Agrawal wrote:
> As I'll no longer be working with Arm, add a mailmap entry so any mail
> directed towards me reaches the appropriate mailbox.
>
> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
I'll pick this up for 4.20-rc2 (unless Linus applies it directly).
Good luck with your new job! ;)
--
Catalin
prev parent reply other threads:[~2018-11-05 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 16:57 [PATCH] mailmap: Update email for Punit Agrawal Punit Agrawal
2018-11-02 17:13 ` Will Deacon
2018-11-05 10:02 ` Catalin Marinas [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:
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=20181105100202.GA23421@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=punit.agrawal@arm.com \
--cc=punitagrawal@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/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).