From: Robert Richter <rrichter@marvell.com>
To: Arnd Bergmann <arnd@arndb.de>, arm soc <arm@kernel.org>
Cc: Jan Glauber <jglauber@marvell.com>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
George Cherian <gcherian@marvell.com>,
"Ganapatrao Prabhakerrao Kulkarni" <gkulkarni@marvell.com>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"soc@kernel.org" <soc@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] MAINTAINERS: update Cavium ThunderX drivers
Date: Tue, 19 Nov 2019 19:16:20 +0000 [thread overview]
Message-ID: <20191119191612.bnyy4agiaoakpizz@rric.localdomain> (raw)
In-Reply-To: <20191119165549.14570-2-rrichter@marvell.com>
On 19.11.19 16:56:24, Robert Richter wrote:
> From: Jan Glauber <jglauber@marvell.com>
>
> Remove my maintainer entries for ThunderX drivers as I'm moving on
> and won't have access to ThunderX hardware anymore and add Robert.
> Also remove the obsolete addresses of David Daney and Steven Hill.
>
> Add an entry to .mailmap for my various email addresses.
This patch is a leftover and shouldn't have been sent. The actual
patch has a slightly modified subject:
[PATCH 1/2] MAINTAINERS: Update Cavium ThunderX drivers
I have sent a v2 already that supersedes this series.
Thanks,
-Robert
next prev parent reply other threads:[~2019-11-19 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191119165549.14570-1-rrichter@marvell.com>
2019-11-19 16:56 ` [PATCH 1/2] MAINTAINERS: update Cavium ThunderX drivers Robert Richter
2019-11-19 19:16 ` Robert Richter [this message]
2019-11-19 16:56 ` [PATCH 1/2] MAINTAINERS: Update " Robert Richter
2019-11-19 17:02 ` Baruch Siach
2019-11-19 18:47 ` Robert Richter
2019-11-19 16:56 ` [PATCH 2/2] MAINTAINERS: Switch to Marvell addresses Robert Richter
2019-11-19 17:14 ` Joe Perches
2019-11-19 18:50 ` Robert Richter
2019-11-19 19:56 ` Joe Perches
2019-11-19 20:23 ` Robert Richter
2019-11-19 21:12 ` 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=20191119191612.bnyy4agiaoakpizz@rric.localdomain \
--to=rrichter@marvell.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=gcherian@marvell.com \
--cc=gkulkarni@marvell.com \
--cc=jglauber@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgoutham@marvell.com \
--cc=soc@kernel.org \
--cc=will@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).