From: Sachin Kamat <sachin.kamat@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: broonie@kernel.org, lgirdwood@gmail.com, sachin.kamat@linaro.org
Subject: [PATCH 07/16] regulator: 88pm8607: Use of_get_child_by_name
Date: Fri, 14 Feb 2014 17:19:53 +0530 [thread overview]
Message-ID: <1392378602-32302-7-git-send-email-sachin.kamat@linaro.org> (raw)
In-Reply-To: <1392378602-32302-1-git-send-email-sachin.kamat@linaro.org>
of_find_node_by_name walks the allnodes list, and can thus walk
outside of the parent node. Use of_get_child_by_name instead.
Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
---
drivers/regulator/88pm8607.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/88pm8607.c b/drivers/regulator/88pm8607.c
index f704d83c93c4..fa99bfccaa6b 100644
--- a/drivers/regulator/88pm8607.c
+++ b/drivers/regulator/88pm8607.c
@@ -322,7 +322,7 @@ static int pm8607_regulator_dt_init(struct platform_device *pdev,
nproot = of_node_get(pdev->dev.parent->of_node);
if (!nproot)
return -ENODEV;
- nproot = of_find_node_by_name(nproot, "regulators");
+ nproot = of_get_child_by_name(nproot, "regulators");
if (!nproot) {
dev_err(&pdev->dev, "failed to find regulators node\n");
return -ENODEV;
--
1.7.9.5
next prev parent reply other threads:[~2014-02-14 11:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 11:49 [PATCH 01/16] regulator: max77686: Use of_get_child_by_name Sachin Kamat
2014-02-14 11:49 ` [PATCH 02/16] regulator: max77693: " Sachin Kamat
2014-02-14 21:08 ` Mark Brown
2014-02-14 11:49 ` [PATCH 03/16] regulator: max8660: " Sachin Kamat
2014-02-14 21:09 ` Mark Brown
2014-02-14 11:49 ` [PATCH 04/16] regulator: max8907: " Sachin Kamat
2014-02-14 21:10 ` Mark Brown
2014-02-14 11:49 ` [PATCH 05/16] regulator: max8925: " Sachin Kamat
2014-02-14 21:11 ` Mark Brown
2014-02-14 11:49 ` [PATCH 06/16] regulator: max8997: " Sachin Kamat
2014-02-14 21:11 ` Mark Brown
2014-02-14 11:49 ` Sachin Kamat [this message]
2014-02-14 21:14 ` [PATCH 07/16] regulator: 88pm8607: " Mark Brown
2014-02-14 11:49 ` [PATCH 08/16] regulator: act8865: " Sachin Kamat
2014-02-14 21:15 ` Mark Brown
2014-02-14 11:49 ` [PATCH 09/16] regulator: as3711: " Sachin Kamat
2014-02-14 21:15 ` Mark Brown
2014-02-14 11:49 ` [PATCH 10/16] regulator: da9052: " Sachin Kamat
2014-02-14 21:16 ` Mark Brown
2014-02-14 11:49 ` [PATCH 11/16] regulator: da9055: " Sachin Kamat
2014-02-14 21:18 ` Mark Brown
2014-02-14 11:49 ` [PATCH 12/16] regulator: da9063: " Sachin Kamat
2014-02-14 21:18 ` Mark Brown
2014-02-14 11:49 ` [PATCH 13/16] regulator: mc13xxx: " Sachin Kamat
2014-02-14 21:19 ` Mark Brown
2014-02-14 11:50 ` [PATCH 14/16] regulator: pfuze100: " Sachin Kamat
2014-02-14 21:20 ` Mark Brown
2014-02-14 11:50 ` [PATCH 15/16] regulator: tps6507x: " Sachin Kamat
2014-02-14 21:21 ` Mark Brown
2014-02-14 11:50 ` [PATCH 16/16] regulator: tps65217: " Sachin Kamat
2014-02-14 21:22 ` Mark Brown
2014-02-14 21:08 ` [PATCH 01/16] regulator: max77686: " 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=1392378602-32302-7-git-send-email-sachin.kamat@linaro.org \
--to=sachin.kamat@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.