All of lore.kernel.org
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL]  Broadcom MAINTAINERS file updates for 3.20 (v3)
Date: Thu, 29 Jan 2015 12:40:23 -0800	[thread overview]
Message-ID: <1422564023-28977-1-git-send-email-f.fainelli@gmail.com> (raw)

The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:

  Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)

are available in the git repository at:

  http://github.com/broadcom/stblinux tags/arm-soc/for-3.20/maintainer

for you to fetch changes up to 5e2aed2746a02f677cc07679407360ab80b4106a:

  MAINTAINERS: add a git entry for BMIPS-based BCM7xxx SoCs (2015-01-29 12:31:30 -0800)

Arnd, Olof, please drop the previous pull request and use this one instead, thanks!

Changes in v3:
- provide working git repositories links

Changes in v2:
- consistently use github.com/broadcom (lower case) everywhere

----------------------------------------------------------------
This pull request contains updates to our MAINTAINERS files for all relevant
Broadcom SoCs: BCM63xx, Cygnus/iProc, ARM & MIPS-based BCM7xxx (brcmstb).

Our new code location for all Broadcom-related kernel activities is now on
http://github.com/broadcom/.

----------------------------------------------------------------
Florian Fainelli (4):
      MAINTAINERS: move BCM63xx ARM-based SoCs git tree
      MAINTAINERS: update Broadcom Cygnus SoC git tree
      MAINTAINERS: add a git entry for BCM7xxx ARM-based SoCs
      MAINTAINERS: add a git entry for BMIPS-based BCM7xxx SoCs

 MAINTAINERS | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

             reply	other threads:[~2015-01-29 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 20:40 Florian Fainelli [this message]
2015-01-29 22:13 ` [GIT PULL] Broadcom MAINTAINERS file updates for 3.20 (v3) 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=1422564023-28977-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.