From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, ralf@linux-mips.org,
f.fainelli@gmail.com, jogo@openwrt.org, cernekee@gmail.com,
simon@fire.lp0.eu
Subject: Re: [PATCH 5/6] MIPS: BMIPS: Add BCM6362 support
Date: Tue, 14 Jun 2016 17:32:58 -0500 [thread overview]
Message-ID: <20160614223258.GA7612@rob-hp-laptop> (raw)
In-Reply-To: <1465803534-25840-5-git-send-email-noltari@gmail.com>
On Mon, Jun 13, 2016 at 09:38:53AM +0200, Álvaro Fernández Rojas wrote:
> BCM6362 is a BMIPS4350 SoC which needs the same fixup as BCM6368 in order to
> enable SMP support.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
> Documentation/devicetree/bindings/mips/brcm/soc.txt | 2 +-
> arch/mips/bmips/setup.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-06-14 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 7:38 [PATCH 1/6] MIPS: BMIPS: add missing console to bcm96358nb4ser Álvaro Fernández Rojas
2016-06-13 7:38 ` [PATCH 2/6] MIPS: BMIPS: Add device tree example for BCM63268 Álvaro Fernández Rojas
2016-06-13 7:38 ` [PATCH 3/6] MIPS: BMIPS: Add BCM3368 support Álvaro Fernández Rojas
2016-06-14 22:32 ` Rob Herring
2016-06-13 7:38 ` [PATCH 4/6] MIPS: BMIPS: Add device tree example for BCM3368 Álvaro Fernández Rojas
2016-06-13 7:38 ` [PATCH 5/6] MIPS: BMIPS: Add BCM6362 support Álvaro Fernández Rojas
2016-06-14 22:32 ` Rob Herring [this message]
2016-06-13 7:38 ` [PATCH 6/6] MIPS: BMIPS: Add device tree example for BCM6362 Álvaro Fernández Rojas
2016-06-14 14:46 ` Jonas Gorski
2016-06-14 14:38 ` [PATCH 1/6] MIPS: BMIPS: add missing console to bcm96358nb4ser Jonas Gorski
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=20160614223258.GA7612@rob-hp-laptop \
--to=robh@kernel.org \
--cc=cernekee@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jogo@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=noltari@gmail.com \
--cc=ralf@linux-mips.org \
--cc=simon@fire.lp0.eu \
/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
Powered by JetHome