From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: of_get_regulation_constraints: Use node name as fallback
Date: Mon, 23 Sep 2013 22:28:27 +0200 [thread overview]
Message-ID: <5240A46B.3080408@metafoo.de> (raw)
In-Reply-To: <20130923101551.GY21013@sirena.org.uk>
On 09/23/2013 12:15 PM, Mark Brown wrote:
> On Sun, Sep 22, 2013 at 12:47:34PM +0200, Lars-Peter Clausen wrote:
>> If the "regulator-name" property is not present use the name of the devicetree
>> node as a fallback.
>
> You're not supposed to use the node name for anything, the goal is that
> it's entirely ornamental noise. Which is a bit annoying but there we
> are.
>
Is this documented somewhere? I'd be interested in the rationale behind this.
next prev parent reply other threads:[~2013-09-23 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 10:47 [PATCH] regulator: of_get_regulation_constraints: Use node name as fallback Lars-Peter Clausen
2013-09-23 10:15 ` Mark Brown
2013-09-23 20:28 ` Lars-Peter Clausen [this message]
2013-09-23 23:33 ` Mark Brown
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=5240A46B.3080408@metafoo.de \
--to=lars@metafoo.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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