From: Will Deacon <will@kernel.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: virtio-dev@lists.oasis-open.org, lorenzo.pieralisi@arm.com,
mst@redhat.com, maz@kernel.org, joro@8bytes.org,
virtualization@lists.linux-foundation.org,
iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Update my email address
Date: Mon, 22 Jul 2019 14:56:53 +0100 [thread overview]
Message-ID: <20190722135652.se2ba5ithml37dtz@willie-the-truck> (raw)
In-Reply-To: <20190722134438.31003-1-jean-philippe@linaro.org>
On Mon, Jul 22, 2019 at 02:44:40PM +0100, Jean-Philippe Brucker wrote:
> Update MAINTAINERS and .mailmap with my @linaro.org address, since I
> don't have access to my @arm.com address anymore.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> .mailmap | 1 +
> MAINTAINERS | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/.mailmap b/.mailmap
> index 0fef932de3db..8ce554b9c9f1 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -98,6 +98,7 @@ Jason Gunthorpe <jgg@ziepe.ca> <jgunthorpe@obsidianresearch.com>
> Javi Merino <javi.merino@kernel.org> <javi.merino@arm.com>
> <javier@osg.samsung.com> <javier.martinez@collabora.co.uk>
> Jean Tourrilhes <jt@hpl.hp.com>
> +<jean-philippe@linaro.org> <jean-philippe.brucker@arm.com>
> Jeff Garzik <jgarzik@pretzel.yyz.us>
> Jeff Layton <jlayton@kernel.org> <jlayton@redhat.com>
> Jeff Layton <jlayton@kernel.org> <jlayton@poochiereds.net>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 783569e3c4b4..bded78c84701 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17123,7 +17123,7 @@ F: drivers/virtio/virtio_input.c
> F: include/uapi/linux/virtio_input.h
>
> VIRTIO IOMMU DRIVER
> -M: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> +M: Jean-Philippe Brucker <jean-philippe@linaro.org>
> L: virtualization@lists.linux-foundation.org
> S: Maintained
> F: drivers/iommu/virtio-iommu.c
Thanks (and your new address is easier to remember ;). I can take this one
via arm64, since I already have a bunch of MAINTAINERS updates queued for
-rc2.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-22 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 13:44 [PATCH] MAINTAINERS: Update my email address Jean-Philippe Brucker
2019-07-22 13:56 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-24 10:12 [PATCH] MAINTAINERS: update " kaloz
2019-07-18 19:24 [PATCH] MAINTAINERS: Update " Maxime Ripard
2019-07-23 9:26 ` Maxime Ripard
2019-07-17 10:32 Julien Thierry
2019-07-17 11:36 ` Marc Zyngier
2019-07-17 11:43 ` Will Deacon
2019-06-15 8:21 Hanjun Guo
2019-06-17 7:56 ` Marc Zyngier
2019-06-17 8:44 ` Hanjun Guo
2012-03-06 0:58 [PATCH] MAINTAINERS: update " Stephen Warren
2012-03-07 22:56 ` Olof Johansson
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=20190722135652.se2ba5ithml37dtz@willie-the-truck \
--to=will@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=mst@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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