linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
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>,
	Vladimir Zapolskiy <vz@mleia.com>,
	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 15:19:57 +0200	[thread overview]
Message-ID: <CAK8P3a0YjbCHRHaTzev-rwi5qM3aBeFUUObL1dPKww_o_J_2vw@mail.gmail.com> (raw)
In-Reply-To: <1537764195-19117-1-git-send-email-daniel.lezcano@linaro.org>

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).

       Arnd

> ---
>  MAINTAINERS | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 67e877c..f3612f6b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1599,9 +1599,8 @@ L:        linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>  S:     Maintained
>
>  ARM/LPC18XX ARCHITECTURE
> -M:     Joachim Eastwood <manabian@gmail.com>
>  L:     linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> -S:     Maintained
> +S:     Orphan
>  F:     arch/arm/boot/dts/lpc43*
>  F:     drivers/clk/nxp/clk-lpc18xx*
>  F:     drivers/clocksource/timer-lpc32xx.c
> --
> 2.7.4
>

  reply	other threads:[~2018-09-24 13:20 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 [this message]
2018-09-24 15:19   ` Vladimir Zapolskiy
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=CAK8P3a0YjbCHRHaTzev-rwi5qM3aBeFUUObL1dPKww_o_J_2vw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=arm@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=slemieux.tyco@gmail.com \
    --cc=vz@mleia.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).