public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Broadcom SoC changes for 4.2 (part 2)
Date: Mon, 01 Jun 2015 17:55:34 +0200	[thread overview]
Message-ID: <2256694.0KQLO0mjvp@wuerfel> (raw)
In-Reply-To: <1432936501-20453-1-git-send-email-f.fainelli@gmail.com>

On Friday 29 May 2015 14:55:01 Florian Fainelli wrote:
> This pull request contains the following changes for Broadcom SoCs:
> 
> - Dan fixes an error path in the BCM63xx SMP code
> 
> - Ray adds the relevant Kconfig selects to enable the Broadcom NAND driver on Cygnus
> 
> - Kevin provides a change to the Broadcom GISB arbiter driver to make it work with
>   MIPS-based big-endian STB SoCs (this was a long-standing change that had dependencies on
>   code in drivers/of/*)
> 
> - Gregory enables the use of GPIOLIB for brcmstb SoCs and bumps the number of GPIOs for
>   these platforms
> 
> 

Pulled into next/soc, thanks!

	Arnd

      reply	other threads:[~2015-06-01 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 21:55 [GIT PULL] Broadcom SoC changes for 4.2 (part 2) Florian Fainelli
2015-06-01 15:55 ` Arnd Bergmann [this message]

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=2256694.0KQLO0mjvp@wuerfel \
    --to=arnd@arndb.de \
    --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