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: [GIT PULL #2] ARM: BCM: Broadcom BCM63138 support
Date: Thu, 25 Sep 2014 14:33:32 -0700	[thread overview]
Message-ID: <54248A2C.9000203@gmail.com> (raw)
In-Reply-To: <1410977394-27987-1-git-send-email-f.fainelli@gmail.com>

On 09/17/2014 11:09 AM, Florian Fainelli wrote:
> Changes in v2:
> - rebased against v3.17-rc1
> - added Arnd's Acked-by
> - added a proper tag to pull from
> 
> Thank you!
> 
> The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
> 
>   Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
> 
> are available in the git repository at:
> 
>   http://github.com/brcm/linux.git tags/bcm63138-v4
> 
> for you to fetch changes up to e076e96227ef6b5b66cfdd79e75401bd2f6d532f:
> 
>   MAINTAINERS: add entry for the Broadcom BCM63xx ARM SoCs (2014-09-17 10:56:08 -0700)

Now that we have hopefully cleared out the mach-bcm situation, is there
anything blocking this pull request?

Thanks!

> 
> ----------------------------------------------------------------
> Florian Fainelli (5):
>       ARM: BCM63XX: add basic support for the Broadcom BCM63138 DSL SoC
>       ARM: BCM63XX: add low-level UART debug support
>       ARM: BCM63XX: add BCM63138 minimal Device Tree
>       ARM: BCM63XX: add BCM963138DVT Reference platform DTS
>       MAINTAINERS: add entry for the Broadcom BCM63xx ARM SoCs
> 
>  .../devicetree/bindings/arm/bcm/bcm63138.txt       |   9 ++
>  MAINTAINERS                                        |   8 ++
>  arch/arm/Kconfig.debug                             |  18 ++-
>  arch/arm/boot/dts/Makefile                         |   1 +
>  arch/arm/boot/dts/bcm63138.dtsi                    | 134 +++++++++++++++++++++
>  arch/arm/boot/dts/bcm963138dvt.dts                 |  30 +++++
>  arch/arm/include/debug/bcm63xx.S                   |  33 +++++
>  arch/arm/mach-bcm/Kconfig                          |  17 +++
>  arch/arm/mach-bcm/Makefile                         |   3 +
>  arch/arm/mach-bcm/bcm63xx.c                        |  27 +++++
>  10 files changed, 278 insertions(+), 2 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/arm/bcm/bcm63138.txt
>  create mode 100644 arch/arm/boot/dts/bcm63138.dtsi
>  create mode 100644 arch/arm/boot/dts/bcm963138dvt.dts
>  create mode 100644 arch/arm/include/debug/bcm63xx.S
>  create mode 100644 arch/arm/mach-bcm/bcm63xx.c
> 

  reply	other threads:[~2014-09-25 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 18:09 [GIT PULL #2] ARM: BCM: Broadcom BCM63138 support Florian Fainelli
2014-09-25 21:33 ` Florian Fainelli [this message]
2014-09-25 21:51 ` Arnd Bergmann

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=54248A2C.9000203@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).