From: sbranden@broadcom.com (Scott Branden)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] dt-bindings: Add new SoCs to bcm4708 DT bindings
Date: Fri, 16 Oct 2015 15:39:11 -0700 [thread overview]
Message-ID: <56217C8F.8090003@broadcom.com> (raw)
In-Reply-To: <56216F39.3020400@hauke-m.de>
On 15-10-16 02:42 PM, Hauke Mehrtens wrote:
> On 10/16/2015 12:24 AM, Jon Mason wrote:
>> Add the 4708, 4709, and 53012 SoCs to the the documentation for the
>> Broadcom Northstar device tree bindings.
>>
>> Signed-off-by: Jon Mason <jonmason@broadcom.com>
> Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
Acked-by: Scott Branden <sbranden@broadcom.com>
>
>> ---
>> Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
>> index 6b0f49f..8608a77 100644
>> --- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
>> +++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
>> @@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties:
>>
>> Required root node property:
>>
>> +bcm4708
>> compatible = "brcm,bcm4708";
>> +
>> +bcm4709
>> +compatible = "brcm,bcm4709";
>> +
>> +bcm53012
>> +compatible = "brcm,bcm53012";
>>
>
next prev parent reply other threads:[~2015-10-16 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 22:24 [PATCH v3 1/2] dt-bindings: Add new SoCs to bcm4708 DT bindings Jon Mason
2015-10-15 22:24 ` [PATCH v3 2/2] ARM: dts: bcm5301x: Add BCM SVK DT files Jon Mason
2015-10-16 21:41 ` Hauke Mehrtens
2015-10-16 22:38 ` Scott Branden
2015-10-16 22:42 ` Hauke Mehrtens
2015-10-16 22:51 ` Scott Branden
2015-10-21 9:07 ` Sudeep Holla
2015-10-16 21:42 ` [PATCH v3 1/2] dt-bindings: Add new SoCs to bcm4708 DT bindings Hauke Mehrtens
2015-10-16 22:39 ` Scott Branden [this message]
2015-10-21 2:21 ` Rob Herring
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=56217C8F.8090003@broadcom.com \
--to=sbranden@broadcom.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).