linux-kernel - Re: [PATCH] MAINTAINERS: Assign myself as a maintainer of ARM/LPC18XX architecture

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 11 Oct 2018 16:11:42 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Vladimir Zapolskiy <vz@...ia.com>
Cc:     arm@...nel.org, Joachim Eastwood <manabian@...il.com>,
        Olof Johansson <olof@...om.net>,
        Mark Rutland <mark.rutland@....com>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Assign myself as a maintainer of ARM/LPC18XX architecture

On 10/11/18, Vladimir Zapolskiy <vz@...ia.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@...ia.com>
> Cc: Joachim Eastwood <manabian@...il.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!

      Arnd