From: Rob Herring <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: broonie@kernel.org, devicetree@vger.kernel.org,
Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH] dt-bindings: pfuze100: Make the node name generic
Date: Tue, 8 May 2018 11:08:11 -0500 [thread overview]
Message-ID: <20180508160811.GA21925@rob-hp-laptop> (raw)
In-Reply-To: <1525483033-20575-1-git-send-email-festevam@gmail.com>
On Fri, May 04, 2018 at 10:17:13PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@nxp.com>
>
> According to Devicetree Specification v0.2 document:
>
> "The name of a node should be somewhat generic, reflecting the function
> of the device and not its precise programming model."
>
> Do as suggested in the binding example.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> ---
> Documentation/devicetree/bindings/regulator/pfuze100.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2018-05-08 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 1:17 [PATCH] dt-bindings: pfuze100: Make the node name generic Fabio Estevam
2018-05-08 16:08 ` Rob Herring [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=20180508160811.GA21925@rob-hp-laptop \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
/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