linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mach-bcm: offer a new maintainer and process
Date: Fri, 19 Sep 2014 11:17:11 -0700	[thread overview]
Message-ID: <1411150632-25695-1-git-send-email-f.fainelli@gmail.com> (raw)

Hi all,

As some of you may have seen in the news, Broadcom has recently stopped
its mobile SoC activities. Upstream support for Broadcom's Mobile SoCs
was an effort initially started by Christian Daudt and his team, and then
continued by Alex Eleder and Matter Porter assigned to a particular landing
team within Linaro to help Broadcom doing so.

As part of this effort, Christian and Matt volunteered for centralizing pull
requests coming from the arch/arm/mach-bcm/* directory and as of today, they
are still responsible for merging mach-bcm pull requests coming from brcmstb,
bcm5301x, bcm2835 and bcm63xx, creating an intermediate layer to the arm-soc
tree.

Following the mobile group shut down, our group (in which Brian, Gregory, Marc,
Kevin and myself are) inherited these mobile SoC platforms, although at this
point we cannot comment on the future of mobile platforms, we know that our
Linaro activities have been stopped.

We have not heard much from Christian and Matt in a while, and some of our pull
requests have been stalling as a result. We would like to offer both a new
maintainer for the mobile platforms as well as reworking the pull request
process:

- our group has now full access to these platforms, putting us in the best
  position to support Mobile SoCs questions

- over time, we think that the brcmstb, bcm5301x, bcm63xx and now Cygnus code
  bases will represent the major bulk of the mach-bcm code changes submitted,
  mobile SoCs being in deep maintenance mode

- we want to keep our submission pace high, and keep a smooth and responsive
  process in place for other maintainers such as Hauke Merthens and Stephen
  Warren and now Scott Branden and his team for Cygnus/Northstar+.

- there is little to no code sharing within mach-bcm, so we think each group
  of maintainers should send individual pull requests towards Arnd and Olof,
  the only conflicts they should ever have to resolve are for the Makefile and
  Kconfig files, not different than any other pull requests

Ideally, we would like Christian and Matt to acknowledge that change, if we
cannot get an answer within the next 3 weeks, we think this change
should go in to unblock the current situation.

Florian Fainelli (1):
  MAINTAINERS: add a third maintainer to mach-bcm

 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

-- 
1.9.1

             reply	other threads:[~2014-09-19 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 18:17 Florian Fainelli [this message]
2014-09-19 18:17 ` [PATCH] MAINTAINERS: add a third maintainer to mach-bcm Florian Fainelli
2014-09-19 18:24   ` Scott Branden
2014-09-19 18:27   ` Brian Norris
2014-09-23 12:48   ` Matt Porter
2014-09-23  5:03 ` [PATCH] ARM: mach-bcm: offer a new maintainer and process Olof Johansson
2014-09-23  5:22   ` Florian Fainelli
2014-09-23 12:54   ` Matt Porter
2014-09-23 15:00     ` Scott Branden
2014-09-23 15:26       ` Matt Porter
2014-09-23 16:24       ` Olof Johansson

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=1411150632-25695-1-git-send-email-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).