From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Stefan Wahren <wahrenst@gmx.net>,
linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: Re: BCM2835 maintainership
Date: Thu, 21 Nov 2019 09:42:21 -0800 [thread overview]
Message-ID: <51d2c5e6-7cd5-02a1-77c9-c96b27a04242@gmail.com> (raw)
In-Reply-To: <52c0e259-9130-fa56-a036-dec95d4bd7d4@i2se.com>
On 11/21/19 1:56 AM, Stefan Wahren wrote:
> Am 20.11.19 um 22:54 schrieb Florian Fainelli:
>> On 11/20/19 3:38 AM, Stefan Wahren wrote:
>>> Hello,
>>>
>>> i need to announce that i step back as BCM2835 maintainer with the end
>>> of this year. Maintainership was a fun ride, but at the end i noticed
>>> that it needed more time for doing it properly than my available spare time.
>>>
>>> Nicolas Saenz Julienne is pleased be my successor and i wish him all the
>>> best on his way.
>>>
>>> Finally i want to thank all the countless contributors and maintainers
>>> for helping to integrate the Raspberry Pi into the mainline Kernel.
>> Thanks Stefan, it has been great working with you on BCM2835
>> maintenance. Do you mind making this statement official with a
>> MAINTAINERS file update?
>
> Sure, but first we should define the future BCM2835 git repo. I like to
> hear Eric's opinion about that, since he didn't step back.
How about we move out of github.com/Broadcom/stblinux as well as Eric's
tree and get a group maintained repository on kernel.org, something like
kernel/git/broadcom/linux.git?
Then we can continue the existing processe whereby BCM2835 gets pulled
into other Broadcom SoC pull requests.
How does that sound?
--
Florian
next prev parent reply other threads:[~2019-11-21 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 11:38 BCM2835 maintainership Stefan Wahren
2019-11-20 14:11 ` Phil Elwell
2019-11-20 20:20 ` Nicolas Saenz Julienne
2019-11-20 21:54 ` Florian Fainelli
2019-11-21 9:56 ` Stefan Wahren
2019-11-21 17:42 ` Florian Fainelli [this message]
2019-11-21 17:51 ` Stefan Wahren
2019-11-21 18:03 ` Florian Fainelli
2019-11-21 22:23 ` Eric Anholt
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=51d2c5e6-7cd5-02a1-77c9-c96b27a04242@gmail.com \
--to=f.fainelli@gmail.com \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=stefan.wahren@i2se.com \
--cc=wahrenst@gmx.net \
/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).