linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] MAINTAINERS: update brcmstb entries
Date: Wed, 14 Jan 2015 16:13:40 -0800	[thread overview]
Message-ID: <CAN8TOE_uHUFuyofTYFzWioB7TkCqx2sLYk2bbrV06EKOMvzYRg@mail.gmail.com> (raw)
In-Reply-To: <54595FED.6000409@gmail.com>

Since I found this in my inbox during garbage collection...

On Tue, Nov 4, 2014 at 3:23 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> On 11/04/2014 02:56 PM, Grant Likely wrote:
>> On Tue, Nov 4, 2014 at 10:48 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>>> On 11/04/2014 12:45 PM, Olof Johansson wrote:
>>>> On Tue, Oct 28, 2014 at 11:44:54AM -0700, Florian Fainelli wrote:
>>>>> Remove Marc Carino from the brcmstb maintainers list and add Gregory
>>>>> Fong and myself as new maintainers for the brcmstb platform.
>>>>>
>>>>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>>>>> ---
>>>>>  MAINTAINERS | 3 ++-
>>>>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>>> index dab92a78d1d5..33a8b31e03f0 100644
>>>>> --- a/MAINTAINERS
>>>>> +++ b/MAINTAINERS
>>>>> @@ -2093,8 +2093,9 @@ F:     arch/arm/mach-bcm/bcm63xx.c
>>>>>  F:  arch/arm/include/debug/bcm63xx.S
>>>>>
>>>>>  BROADCOM BCM7XXX ARM ARCHITECTURE
>>>>> -M:  Marc Carino <marc.ceeeee@gmail.com>
>>>>>  M:  Brian Norris <computersforpeace@gmail.com>
>>>>> +M:  Gregory Fong <gregory.0xf0@gmail.com>
>>>>> +M:  Florian Fainelli <f.fainelli@gmail.com>
>>>>
>>>> You're removing Marc here, but I don't see an ack from him, nor has
>>>> he been cc:d on the patch. It's common practice for people to agree to
>>>> being removed. Can you please make sure we get an ack from him on this,
>>>> maybe by reposting and cc:ing him?
>>>
>>> Marc is no longer with Broadcom, do you still want him to ack this?
>>
>> Yes, absolutely. Maintainership is entrusted to an individual, not
>> their employer. We've had many situations where someone has continued
>> to maintain a platform even after changing employment. So, yes, there
>> needs to be an ack from Marc.
>
> He is CC'd, now. Marc, please Ack this if you are okay with the change.

Can we add a "Not-nacked-by" tag and proceed? Marc is obviously not
involved here any more. I figure removing expired maintainers should
be a little easier than removing SCOTUS judges.

Brian

  reply	other threads:[~2015-01-15  0:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 18:44 [PATCH 0/2] MAINTAINERS: brcmstb entry updates Florian Fainelli
2014-10-28 18:44 ` [PATCH 1/2] MAINTAINERS: update brcmstb entries Florian Fainelli
2014-10-31 20:14   ` Gregory Fong
2014-11-04 20:45   ` Olof Johansson
2014-11-04 22:48     ` Florian Fainelli
2014-11-04 22:56       ` Grant Likely
2014-11-04 23:23         ` Florian Fainelli
2015-01-15  0:13           ` Brian Norris [this message]
2015-01-15  1:52             ` Florian Fainelli
2014-10-28 18:44 ` [PATCH 2/2] MAINTAINERS: add entry for the GISB arbiter driver Florian Fainelli
2014-10-29  5:03 ` [PATCH 0/2] MAINTAINERS: brcmstb entry updates Brian Norris

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=CAN8TOE_uHUFuyofTYFzWioB7TkCqx2sLYk2bbrV06EKOMvzYRg@mail.gmail.com \
    --to=computersforpeace@gmail.com \
    --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).