All of lore.kernel.org
 help / color / mirror / Atom feed
From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: extend Raspberry Pi entry
Date: Wed, 01 Feb 2017 11:51:51 -0800	[thread overview]
Message-ID: <87h94dr8o8.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <2fcb0690-861a-1b83-c6d5-dfdef03fa9ab@wwwdotorg.org>

Stephen Warren <swarren@wwwdotorg.org> writes:

> On 01/31/2017 12:49 PM, Eric Anholt wrote:
>> Stephen Warren <swarren@wwwdotorg.org> writes:
>>
>>> On 01/29/2017 01:08 PM, Baruch Siach wrote:
>>>> Add bcm2836 (Raspberry Pi 2) and bcm2837 (Raspberry Pi 3).
>>>
>>>> -BROADCOM BCM2835 ARM ARCHITECTURE
>>>> +BROADCOM BCM2835/BCM2836/BCM2837 ARM ARCHITECTURE
>>> ...
>>>>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi.git
>>>
>>> It would make sense to update that too, if Eric isn't using this.
>>> However, that's a subject for a different patch perhaps.
>>>
>>> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
>>
>> Pulled this patch, sent a followup for the tree location.
>>
>> Thinking of MAINTAINERS, I was wondering if you and Lee were both still
>> interested in being on the list?
>
> To be honest, I was thinking about sending a patch to remove myself 
> since you've been taking care of everything well and I've been too lazy 
> to do anything RPi related recently.

Sounds good.

I've been mulling over a couple of ideas about bcm2835 maintainership of
the tree since LCA: one is asking Florian if he'd like me to just be a
co-maintainer with a limited role within the stblinux tree (bcm2835 is
pretty low traffic, I don't see the need for a separate tree), and the
other is picking up one of the more active current Pi developers as a
co-maintainer within the current tree.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170201/a05e6cb6/attachment.sig>

      reply	other threads:[~2017-02-01 19:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 20:08 [PATCH] MAINTAINERS: extend Raspberry Pi entry Baruch Siach
2017-01-29 20:52 ` Michael Zoran
2017-01-29 21:06   ` Baruch Siach
2017-01-29 21:41     ` Michael Zoran
2017-01-29 21:52       ` Baruch Siach
2017-01-29 22:02         ` Michael Zoran
2017-01-29 22:24           ` Michael Zoran
2017-01-30  7:56             ` Uwe Kleine-König
2017-01-30  8:09               ` Michael Zoran
2017-01-30  8:51                 ` Uwe Kleine-König
2017-01-30  9:01                   ` Michael Zoran
2017-01-29 21:06   ` Stefan Wahren
2017-01-29 21:25   ` Michael Zoran
2017-01-30 17:03 ` Stephen Warren
2017-01-31 19:49   ` Eric Anholt
2017-02-01  5:21     ` Stephen Warren
2017-02-01 19:51       ` Eric Anholt [this message]

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=87h94dr8o8.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --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 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.