From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Assign myself as a maintainer of ARM/LPC18XX architecture
Date: Thu, 11 Oct 2018 16:20:49 +0200 [thread overview]
Message-ID: <5bd0530d-13d9-d25d-d0f4-f48e39174991@linaro.org> (raw)
In-Reply-To: <CAK8P3a3pbpEX1BjKvn179pTYtYEtiQnd=SmD5NYkAtpdZAonkA@mail.gmail.com>
On 11/10/2018 16:11, Arnd Bergmann wrote:
> On 10/11/18, Vladimir Zapolskiy <vz@mleia.com> wrote:
>> To all appearance Joachim Eastwood abandoned the maintenance of NXP
>> LPC18xx/LPC43xx archtecture about two years ago, and for me it would be
>> possible to continue the support, fortunately the quality of platform
>> drivers written by Joachim is exceptionally high.
>>
>> The change is based on https://lkml.org/lkml/2018/9/24/1398 discussion.
>>
>> At the same time two redundant explicit driver file paths are dropped
>> from the list, clk-lpc18xx* drivers are covered by "lpc18xx" search
>> pattern and timer-lpc32xx driver is covered by "lpc32xx" pattern and it
>> goes into ARM/LPC32XX entry, which is also under my wing, in other words
>> LPC18xx/LPC43xx clocksource and CCF drivers will remain maintained.
>>
>> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
>> Cc: Joachim Eastwood <manabian@gmail.com>
>> ---
>
> I could not automatically apply this with 'git am', not sure what the
> problem was, but I managed to apply it by patching the file manually.
>
> Thanks for taking over the platform!
Yes, thanks !
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2018-10-11 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 12:31 [PATCH] MAINTAINERS: Assign myself as a maintainer of ARM/LPC18XX architecture Vladimir Zapolskiy
2018-10-11 14:11 ` Arnd Bergmann
2018-10-11 14:20 ` Daniel Lezcano [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=5bd0530d-13d9-d25d-d0f4-f48e39174991@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).