From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dt-bindings: brcm: rationalize Broadcom documentation naming
Date: Wed, 18 Mar 2015 13:42:32 -0600 [thread overview]
Message-ID: <5509D528.1080208@wwwdotorg.org> (raw)
In-Reply-To: <1426706645-19313-1-git-send-email-sbranden@broadcom.com>
On 03/18/2015 01:24 PM, Scott Branden wrote:
> This patchset attempts to standarize the naming of dt-bindings
> documents based on the Broadcom vendor prefix of brcm.
>
> Although there are no guidelines currently present for how to name
> the dt-bindings document the "vendor,binding.txt" style is in use by
> some of the other vendors.
Conceptually I'm fine with this.
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
The only comment I have is that some bindings refer to other bindings,
e.g. an I2C controller binding might refer to the core I2C binding to
define core I2C properties. Since this patch moves a couple files
between directories, did you double-check that none of the pathnames in
those references need fixing up?
next prev parent reply other threads:[~2015-03-18 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 19:24 [PATCH] dt-bindings: brcm: rationalize Broadcom documentation naming Scott Branden
2015-03-18 19:42 ` Stephen Warren [this message]
2015-03-18 21:53 ` Scott Branden
2015-03-18 22:03 ` Stephen Warren
2015-03-18 22:08 ` Scott Branden
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=5509D528.1080208@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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).