linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Brand <chris.brand@broadcom.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sebastian Reichel <sre@kernel.org>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Russell King <linux@armlinux.org.uk>,
	BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	devicetree@vger.kernel.org,
	Raymond Ngun <raymond.ngun@broadcom.com>,
	Markus Mayer <markus.mayer@broadcom.com>
Subject: Re: [PATCH 0/6] Support BCM23550 SoC
Date: Mon, 9 May 2016 15:31:31 -0700	[thread overview]
Message-ID: <CAMsMSK-MwY6HDmb45vj6g2BTM9yk7+g5oP0hEm9gk6Gi7f+XjA@mail.gmail.com> (raw)
In-Reply-To: <6872671.Czyv7J9iJZ@wuerfel>

On Thu, May 5, 2016 at 2:09 PM, Arnd Bergmann <arnd@arndb.de> wrote:
[...]
> Looks really nice overall, I only found one tiny detail I commented on
> for patch 6.

Thanks!

> I'm glad to see work on the old chips resume, are you working on new
> code for it as well, or just upstreaming the patches that were already
> done in the past?


This is new work. It was actually a good testament to the value of
upstreaming that it was so easy to bring up a 4.6 kernel on this chip.

Chris

      reply	other threads:[~2016-05-09 22:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 20:48 [PATCH 0/6] Support BCM23550 SoC Chris Brand
2016-05-05 20:48 ` [PATCH 1/6] power: Introduce Broadcom kona reset driver Chris Brand
2016-05-05 20:48 ` [PATCH 2/6] arm: bcm21664: Remove reset code Chris Brand
2016-05-05 20:48 ` [PATCH 3/6] docs: Document BCM23550 bindings Chris Brand
2016-05-09 19:41   ` Rob Herring
2016-05-09 22:27     ` Chris Brand
2016-05-05 20:48 ` [PATCH 4/6] arm: Add support for Broadcom BCM23550 SoC Chris Brand
2016-05-05 20:48 ` [PATCH 5/6] arm: BCM23550 SMP support Chris Brand
2016-05-05 20:48 ` [PATCH 6/6] arm: dt: bcm23550: Add device tree files Chris Brand
2016-05-05 21:05   ` Arnd Bergmann
2016-05-06 17:49     ` Chris Brand
2016-05-05 21:09 ` [PATCH 0/6] Support BCM23550 SoC Arnd Bergmann
2016-05-09 22:31   ` Chris Brand [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=CAMsMSK-MwY6HDmb45vj6g2BTM9yk7+g5oP0hEm9gk6Gi7f+XjA@mail.gmail.com \
    --to=chris.brand@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=f.fainelli@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=markus.mayer@broadcom.com \
    --cc=pawel.moll@arm.com \
    --cc=raymond.ngun@broadcom.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=sre@kernel.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).