LKML Archive on
 help / color / Atom feed
From: Stefan Wahren <>
To: Florian Fainelli <>,
	Stefan Wahren <>,, Eric Anholt <>,
	Nicolas Saenz Julienne <>
Subject: Re: BCM2835 maintainership
Date: Thu, 21 Nov 2019 18:51:35 +0100
Message-ID: <> (raw)
In-Reply-To: <>

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 as well as Eric's
> tree and get a group maintained repository on, 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?

  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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git
	git clone --mirror lkml/git/8.git
	git clone --mirror lkml/git/9.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/ \
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone