From: Vladimir Zapolskiy <vz@mleia.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Roland Stigge <stigge@antcom.de>,
Russell King <linux@arm.linux.org.uk>,
Kevin Hilman <khilman@kernel.org>,
linux-kernel@vger.kernel.org,
Sylvain Lemieux <slemieux.tyco@gmail.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC
Date: Fri, 29 Apr 2016 03:02:30 +0300 [thread overview]
Message-ID: <5722A496.90806@mleia.com> (raw)
In-Reply-To: <3148840.0dvKHvK2Ga@wuerfel>
On 29.04.2016 02:14, Arnd Bergmann wrote:
> On Friday 29 April 2016 02:10:32 Vladimir Zapolskiy wrote:
>> Hi Arnd,
>>
>> On 27.04.2016 12:39, Arnd Bergmann wrote:
>>> On Wednesday 27 April 2016 02:55:16 Vladimir Zapolskiy wrote:
>>>> Roland Stigge added initial support of NXP LPC32xx SoC series and
>>>> first boards powered by it, but for a while since v3.18-rc1 the
>>>> SoC support is unmaintained and became stale.
>>>>
>>>> Vladimir Zapolskiy and Sylvain Lemieux expressed interest in
>>>> continuation of NXP LPC32xx maintenance, reflect this in MAINTAINERS
>>>> record file for better communication with Linux kernel community.
>>>>
>>>> The maintenance change is in agreement with Arnd Bergmann:
>>>>
>>>
>>> Looks good. Let's give Roland some time to reply (hopefully with
>>> and Ack), and then merge it for 4.7.
>>>
>>
>> to simplify the matter and to legitimate the process somehow I decided
>> not to include this change of maintainers into my last LPC32xx SoC pull
>> request, hence the pull request contains only code changes.
>>
>> In other words please let me explicitly delegate a decision to you or
>> other ARM maintainers when and which way to apply this change. As for
>> me here I would prefer to get Signed-off-by tags from one of you.
>>
>> If I'm worried for nothing, or if you don't consider to pick these
>> changes up directly from linux-arm-kernel@lists.infradead.org, for
>> your convenience I'll send a pull request to arm@kernel.org.
>
> It's all fine with me. My plan so far is to pick up the patches
> separately in a couple of days, but if you send a pull request,
> I'll take that instead. If Roland still wants to be listed in
> the MAINTAINERS file, we can change it again, but I'm considering
> the two of you the primary contacts now.
>
Sounds good, I offload that anxiety from my mind then.
Thank you.
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2016-04-29 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:55 [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC Vladimir Zapolskiy
2016-04-26 23:55 ` [PATCH 1/3] MAINTAINERS: move ARM/NXP LPC32xx record to ARM section Vladimir Zapolskiy
2016-04-26 23:55 ` [PATCH 2/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC Vladimir Zapolskiy
2016-04-26 23:55 ` [PATCH 3/3] MAINTAINERS: add ARM/NXP LPC32XX SoC specific drivers to the section Vladimir Zapolskiy
2016-04-27 9:39 ` [PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC Arnd Bergmann
2016-04-28 23:10 ` Vladimir Zapolskiy
2016-04-28 23:14 ` Arnd Bergmann
2016-04-29 0:02 ` Vladimir Zapolskiy [this message]
2016-05-09 13:37 ` Arnd Bergmann
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=5722A496.90806@mleia.com \
--to=vz@mleia.com \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=slemieux.tyco@gmail.com \
--cc=stigge@antcom.de \
/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