LKML Archive on lore.kernel.org
 help / color / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <wahrenst@gmx.net>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	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 10:03:47 -0800
Message-ID: <6487c38c-505e-99df-2451-c3da4cb02c94@gmail.com> (raw)
In-Reply-To: <902d2270-8081-b21d-e572-627f470beda7@gmx.net>

On 11/21/19 9:51 AM, Stefan Wahren wrote:
> Hi Florian,
> 
> Am 21.11.19 um 18:42 schrieb Florian Fainelli:
>> 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?
> this sounds like a good idea. In case the others agree too, can you take
> care of it?

Certainly, let me work through the process and I will let you know if
that could work.
-- 
Florian

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 11:38 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
2019-11-21 17:51       ` Stefan Wahren
2019-11-21 18:03         ` Florian Fainelli [this message]
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=6487c38c-505e-99df-2451-c3da4cb02c94@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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
	git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
	git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git