linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@mleia.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Joachim Eastwood <manabian@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	gregkh <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sylvain Lemieux <slemieux.tyco@gmail.com>,
	arm-soc <arm@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Set ARM/LPC18XX architecture orphan
Date: Mon, 24 Sep 2018 18:19:45 +0300	[thread overview]
Message-ID: <bfffe304-b42c-b2a2-f164-642469aff640@mleia.com> (raw)
In-Reply-To: <CAK8P3a0YjbCHRHaTzev-rwi5qM3aBeFUUObL1dPKww_o_J_2vw@mail.gmail.com>

Hi Arnd, Joachim,
 
On 09/24/2018 04:19 PM, Arnd Bergmann wrote:
> On Mon, Sep 24, 2018 at 6:43 AM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>>
>> While sending patches around, Joachim Eastwood was Cc'ed but I got an error
>> its mailbox was full and the mail can not be delivered which makes me think
>> there is no body at the other end of the line.
>>
>> After doing some statistics, it appears the latest commit as author/commiter
>> is:
>>
>> commit b16ebc017ebf52a81e5e88743ccd68fc25e99ba9
>> Author: Joachim Eastwood <manabian@gmail.com>
>> Date:   Mon Oct 31 14:45:17 2016 +0000
>>
>> Remove the maintainer entry and set the component as orphan.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> Cc: Arnd Bergmann <arnd@arndb.de>
> 
> Acked-by: Arnd Bergmann <arnd@arndb.de>
> 
> I also checked the github account and any other mails I could
> find from Joachim, which stopped around the same time.
> 
> I've added the lpc32xx maintainers to Cc, as the two platforms are
> related. Maybe they are interested in picking up support for this
> as well, and/or merge the two directories into one (there is only
> one trivial file in mach-lpc18xx, the rest are drivers).
> 

I'm interested in maintenance of lpc18xx/lpc43xx, I have one board
powered by LPC4357, so it would make the maintenance easier for me,
also multiple controllers are equal on lpc18xx/lpc43xx and lpc32xx,
and thus familiar to me.

And I greatly appreciate Joachim's contribution, all platform drivers
written by Joachim are of perfect quality.

I'll send a patch to MAINTAINERS later on.

--
Best wishes,
Vladimir

  reply	other threads:[~2018-09-24 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  4:42 [PATCH] MAINTAINERS: Set ARM/LPC18XX architecture orphan Daniel Lezcano
2018-09-24 13:19 ` Arnd Bergmann
2018-09-24 15:19   ` Vladimir Zapolskiy [this message]
2018-09-24 15:42     ` Arnd Bergmann
2018-09-25 19:25       ` Olof Johansson

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=bfffe304-b42c-b2a2-f164-642469aff640@mleia.com \
    --to=vz@mleia.com \
    --cc=akpm@linux-foundation.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manabian@gmail.com \
    --cc=mchehab+samsung@kernel.org \
    --cc=slemieux.tyco@gmail.com \
    /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).