linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Elwell <phil@raspberrypi.org>
To: Stefan Wahren <wahrenst@gmx.net>,
	linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: BCM2835 maintainership
Date: Wed, 20 Nov 2019 14:11:46 +0000	[thread overview]
Message-ID: <913cdc73-4b4e-5ea7-80c6-f32d0340f37c@raspberrypi.org> (raw)
In-Reply-To: <68580738-4ecf-3bb7-5720-6e5b6dafcfeb@gmx.net>

Hi Stefan,

On 20/11/2019 11:38, 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.

I'd like to take this opportunity to thank you for being such a champion 
of BCM2835+ and Raspberry Pi. It must have felt like a thankless task at 
times, but you leave the upstream Pi support in a much better state than 
when you started.

Welcome Nicolas - you've been contributing to the mainline kernel almost 
as long as I've been at Raspberry Pi, and you're no stranger to the Pi 
repos on GitHub. I look forward to working with you further.

Phil

  reply	other threads:[~2019-11-20 14:17 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 [this message]
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
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=913cdc73-4b4e-5ea7-80c6-f32d0340f37c@raspberrypi.org \
    --to=phil@raspberrypi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --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).