devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@linaro.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Marc Carino <marc.ceeeee@gmail.com>,
	Christian Daudt <bcm@fixthebug.org>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	Russell King <linux@arm.linux.org.uk>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v6 0/8] ARM: brcmstb: Add Broadcom STB SoC support
Date: Fri, 21 Feb 2014 11:54:21 -0500	[thread overview]
Message-ID: <20140221165421.GM5038@beef> (raw)
In-Reply-To: <CAGVrzcZTHZYaB7sEDxFrP3PzZh0y-daS0gqg2Z4PUzuWGFeiSw@mail.gmail.com>

On Thu, Feb 20, 2014 at 04:41:32PM -0800, Florian Fainelli wrote:
> Matt,
> 
> 2014-02-03 13:30 GMT-08:00 Marc Carino <marc.ceeeee@gmail.com>:
> > This patchset contains the board support package for the
> > Broadcom BCM7445 ARM-based SoC [1]. These changes contain a
> > minimal set of code needed for a BCM7445-based board to boot
> > the Linux kernel.
> 
> If you are happy with this round of changes, can you also carry those
> patches in your tree for 3.15?

I had to add a couple trivial comments on the dts that I missed back in
v2.

More importantly, you'll need to collect some acks on various pieces. In
particular the power/reset driver needs a maintainer ack to go in via
arm-soc. I'd also like to see an ack from Arnd since he provided a lot
of the comments. Also, we need Russell's ack on the debug and proc-v7.S
patches.

I'll note that the drivers/power maintainers aren't cced on this posting
so they probably didn't notice that driver.

-Matt

      reply	other threads:[~2014-02-21 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 21:30 [PATCH v6 0/8] ARM: brcmstb: Add Broadcom STB SoC support Marc Carino
2014-02-03 21:30 ` [PATCH v6 1/8] ARM: brcmstb: add infrastructure for ARM-based Broadcom STB SoCs Marc Carino
2014-02-03 21:30 ` [PATCH v6 2/8] power: reset: Add reboot driver for brcmstb Marc Carino
2014-02-03 21:30 ` [PATCH v6 3/8] ARM: brcmstb: add debug UART for earlyprintk support Marc Carino
2014-02-03 21:30 ` [PATCH v6 4/8] ARM: do CPU-specific init for Broadcom Brahma15 cores Marc Carino
2014-02-03 21:30 ` [PATCH v6 5/8] ARM: brcmstb: add CPU binding for Broadcom Brahma15 Marc Carino
2014-02-03 21:30 ` [PATCH v6 6/8] ARM: brcmstb: add misc. DT bindings for brcmstb Marc Carino
2014-02-03 21:30 ` [PATCH v6 7/8] ARM: brcmstb: gic: add compatible string for Broadcom Brahma15 Marc Carino
2014-02-03 21:30 ` [PATCH v6 8/8] ARM: brcmstb: dts: add a reference DTS for Broadcom 7445 Marc Carino
     [not found]   ` <1391463041-15241-9-git-send-email-marc.ceeeee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-21 16:39     ` Matt Porter
2014-02-21  0:41 ` [PATCH v6 0/8] ARM: brcmstb: Add Broadcom STB SoC support Florian Fainelli
2014-02-21 16:54   ` Matt Porter [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=20140221165421.GM5038@beef \
    --to=mporter@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bcm@fixthebug.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marc.ceeeee@gmail.com \
    --cc=olof@lixom.net \
    /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).