linux-kernel - Re: BCM2835 maintainership

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CADaigPUZQV8VrnXJJxLESQd_6T9+kib015fSTQow9kZmx6szKw@mail.gmail.com>
Date:   Thu, 21 Nov 2019 14:23:43 -0800
From:   Eric Anholt <eric@...olt.net>
To:     Florian Fainelli <f.fainelli@...il.com>
Cc:     Stefan Wahren <wahrenst@....net>,
        Stefan Wahren <stefan.wahren@...e.com>,
        linux-kernel@...r.kernel.org,
        Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Subject: Re: BCM2835 maintainership

On Thu, Nov 21, 2019 at 10:03 AM Florian Fainelli <f.fainelli@...il.com> wrote:
>
> 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.

This all sounds fine to me, though since I'm not active any more we
should probably drop me out of MAINTAINERS while we're doing this
shuffle, too.