From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: lrg@ti.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Fix up a confusing dev_warn when regulator_get fails
Date: Fri, 16 Mar 2012 19:26:57 +0000 [thread overview]
Message-ID: <20120316192654.GK3158@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1331893221-14426-1-git-send-email-rnayak@ti.com>
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
On Fri, Mar 16, 2012 at 03:50:21PM +0530, Rajendra Nayak wrote:
> of_parse_phandle() returns NULL either if the property name
> itself does not exist or if it (exists and) does not
> reference a valid phandle.
Applied, thanks (tweaked the subject line to say DT instead).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-16 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 10:20 [PATCH] regulator: Fix up a confusing dev_warn when regulator_get fails Rajendra Nayak
2012-03-16 19:26 ` Mark Brown [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=20120316192654.GK3158@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rnayak@ti.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