All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Carlo Caione <ccaione@baylibre.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH] MAINTAINERS: Remove myself from the list
Date: Tue, 04 Dec 2018 16:23:32 -0800	[thread overview]
Message-ID: <7h1s6wddob.fsf@baylibre.com> (raw)
In-Reply-To: <eaf25e588c5ab78c607e7168e22871464e7ec8d7.camel@baylibre.com>

Carlo Caione <ccaione@baylibre.com> writes:

> On Mon, 2018-12-03 at 11:21 +0100, Neil Armstrong wrote:
>> On 01/12/2018 16:17, Carlo Caione wrote:
>> > Kevin is basically doing all the work. Remove my name as co-
>> > maintainer.
>> 
>> Sure, but couldn't we move you as reviewer and add Martin as reviewer
>> aswell since he is dedicated to the Meson8X support ?
>> 
>> Or maybe add a separate entry with Kevin as maintainer and Martin as
>> reviewer for Meson8X ?
>
> This. At this point I don't think I will be going to work on the
> Meson8X for a while and Martin proved to be the right guy for this job.
>
> So, let's remove my name from here first and then Martin can add a new
> entry for Meson8X.

Queued for v4.21 (branch: v4.21/soc)

Kevin

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Carlo Caione <ccaione@baylibre.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH] MAINTAINERS: Remove myself from the list
Date: Tue, 04 Dec 2018 16:23:32 -0800	[thread overview]
Message-ID: <7h1s6wddob.fsf@baylibre.com> (raw)
In-Reply-To: <eaf25e588c5ab78c607e7168e22871464e7ec8d7.camel@baylibre.com>

Carlo Caione <ccaione@baylibre.com> writes:

> On Mon, 2018-12-03 at 11:21 +0100, Neil Armstrong wrote:
>> On 01/12/2018 16:17, Carlo Caione wrote:
>> > Kevin is basically doing all the work. Remove my name as co-
>> > maintainer.
>> 
>> Sure, but couldn't we move you as reviewer and add Martin as reviewer
>> aswell since he is dedicated to the Meson8X support ?
>> 
>> Or maybe add a separate entry with Kevin as maintainer and Martin as
>> reviewer for Meson8X ?
>
> This. At this point I don't think I will be going to work on the
> Meson8X for a while and Martin proved to be the right guy for this job.
>
> So, let's remove my name from here first and then Martin can add a new
> entry for Meson8X.

Queued for v4.21 (branch: v4.21/soc)

Kevin

  reply	other threads:[~2018-12-05  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 15:17 [PATCH] MAINTAINERS: Remove myself from the list Carlo Caione
2018-12-01 15:17 ` Carlo Caione
2018-12-03 10:21 ` Neil Armstrong
2018-12-03 10:21   ` Neil Armstrong
2018-12-04 15:00   ` Carlo Caione
2018-12-04 15:00     ` Carlo Caione
2018-12-05  0:23     ` Kevin Hilman [this message]
2018-12-05  0:23       ` Kevin Hilman

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=7h1s6wddob.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=ccaione@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=narmstrong@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.