From: Ralf Baechle <ralf@linux-mips.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: linux-mips@linux-mips.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, f.fainelli@gmail.com,
jogo@openwrt.org, cernekee@gmail.com, simon@fire.lp0.eu
Subject: Re: [PATCH 2/3] MIPS: BMIPS: improve BCM6358 device tree
Date: Mon, 4 Apr 2016 01:10:10 +0200 [thread overview]
Message-ID: <20160403231010.GA6518@linux-mips.org> (raw)
In-Reply-To: <1459685585-11747-2-git-send-email-noltari@gmail.com>
On Sun, Apr 03, 2016 at 02:13:04PM +0200, Álvaro Fernández Rojas wrote:
> - Switch to bcm6345-l1-intc interrupt controller.
> - Add ehci0 and ohci0 nodes.
> - Use proper native-endian syscon property.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
> arch/mips/boot/dts/brcm/bcm6358.dtsi | 29 ++++++++++++++++++++++++-----
Any reason Why didn't you fold this patch into the "[v3,2/2] bmips: add
device tree example for BCM6358" patch of the other series?
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
To: "Álvaro Fernández Rojas"
<noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
jogo-p3rKhJxN3npAfugRpC6u6w@public.gmane.org,
cernekee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
simon-A6De1vDTPLDsq35pWSNszA@public.gmane.org
Subject: Re: [PATCH 2/3] MIPS: BMIPS: improve BCM6358 device tree
Date: Mon, 4 Apr 2016 01:10:10 +0200 [thread overview]
Message-ID: <20160403231010.GA6518@linux-mips.org> (raw)
In-Reply-To: <1459685585-11747-2-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Sun, Apr 03, 2016 at 02:13:04PM +0200, Álvaro Fernández Rojas wrote:
> - Switch to bcm6345-l1-intc interrupt controller.
> - Add ehci0 and ohci0 nodes.
> - Use proper native-endian syscon property.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> arch/mips/boot/dts/brcm/bcm6358.dtsi | 29 ++++++++++++++++++++++++-----
Any reason Why didn't you fold this patch into the "[v3,2/2] bmips: add
device tree example for BCM6358" patch of the other series?
Ralf
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-03 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 12:13 [PATCH 1/3] MIPS: BMIPS: improve BCM6328 device tree Álvaro Fernández Rojas
2016-04-03 12:13 ` [PATCH 2/3] MIPS: BMIPS: improve BCM6358 " Álvaro Fernández Rojas
2016-04-03 23:10 ` Ralf Baechle [this message]
2016-04-03 23:10 ` Ralf Baechle
2016-04-04 8:13 ` Álvaro Fernández Rojas
2016-04-03 12:13 ` [PATCH 3/3] MIPS: BMIPS: improve BCM6368 " Álvaro Fernández Rojas
2016-04-09 10:57 ` [PATCH 1/2] MIPS: BMIPS: improve BCM6328 " Álvaro Fernández Rojas
2016-04-09 10:57 ` Álvaro Fernández Rojas
2016-04-09 10:57 ` [PATCH 2/2] MIPS: BMIPS: improve BCM6368 " Álvaro Fernández Rojas
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=20160403231010.GA6518@linux-mips.org \
--to=ralf@linux-mips.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.