From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
Olof Johansson <olof@lixom.net>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Remove Simon as Renesas SoC Co-Maintainer
Date: Fri, 11 Oct 2019 12:00:29 +0300 [thread overview]
Message-ID: <fc7ec17b-c61b-842e-13d9-1e154ce2a654@cogentembedded.com> (raw)
In-Reply-To: <20191011073515.2933918c@canb.auug.org.au>
Hello!
On 10.10.2019 23:35, Stephen Rothwell wrote:
>> At the end of the v5.3 upstream kernel development cycle, Simon stepped
>> down from his role as Renesas SoC maintainer.
>>
>> Remove his maintainership, git repository, and branch from the
>> MAINTAINERS file, and add an entry to the CREDITS file to honor his
>> work.
>>
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> So, I will remove Simon's Renesas tree from linux-next and rename the
> renesas-geert tree to be renesas, OK?
I thought Geert's new repo is called renesas-devel?
MBR, Sergei
next prev parent reply other threads:[~2019-10-11 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 12:30 [PATCH] MAINTAINERS: Remove Simon as Renesas SoC Co-Maintainer Geert Uytterhoeven
2019-10-10 20:35 ` Stephen Rothwell
2019-10-11 6:24 ` Geert Uytterhoeven
2019-10-11 9:00 ` Sergei Shtylyov [this message]
2019-10-11 9:19 ` Geert Uytterhoeven
2019-10-12 5:49 ` Simon Horman
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=fc7ec17b-c61b-842e-13d9-1e154ce2a654@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@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;
as well as URLs for NNTP newsgroup(s).