From: Stephen Boyd <sboyd@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Andy Gross <agross@codeaurora.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 5/5] regulator: qcom: Tidy up probe()
Date: Mon, 06 Apr 2015 16:40:34 -0700 [thread overview]
Message-ID: <55231972.7010002@codeaurora.org> (raw)
In-Reply-To: <1428363240-2027-6-git-send-email-bjorn.andersson@sonymobile.com>
On 04/06/15 16:34, Bjorn Andersson wrote:
> Tidy up error reporting and move rpm reference retrieval out of the for
> loop for improved readability.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@sonymobile.com>
> ---
>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Thanks.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-04-06 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 23:33 [PATCH v3 0/5] Refactor Qualcomm RPM regulator to single platform_device Bjorn Andersson
2015-04-06 23:33 ` [PATCH v3 1/5] mfd: devicetree: bindings: Add Qualcomm RPM regulator subnodes Bjorn Andersson
2015-04-07 6:39 ` Lee Jones
2015-04-06 23:33 ` [PATCH v3 2/5] regulator: qcom: Don't enable DRMS in driver Bjorn Andersson
2015-04-07 11:11 ` Mark Brown
2015-04-07 13:45 ` Bjorn Andersson
2015-04-06 23:33 ` [PATCH v3 3/5] regulator: qcom: Refactor of-parsing code Bjorn Andersson
2015-04-06 23:33 ` [PATCH v3 4/5] regulator: qcom: Rework to single platform device Bjorn Andersson
2015-04-06 23:40 ` Stephen Boyd
2015-04-06 23:34 ` [PATCH v3 5/5] regulator: qcom: Tidy up probe() Bjorn Andersson
2015-04-06 23:40 ` Stephen Boyd [this message]
2015-04-08 11:23 ` [PATCH v3 0/5] Refactor Qualcomm RPM regulator to single platform_device 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=55231972.7010002@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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).