From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Cc: linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH] regulator: core: Always warn when using a dummy regulator
Date: Fri, 04 Oct 2013 14:59:47 -0600 [thread overview]
Message-ID: <524F2C43.9070302@wwwdotorg.org> (raw)
In-Reply-To: <1380883464-28851-1-git-send-email-broonie@kernel.org>
On 10/04/2013 04:44 AM, Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
>
> This helps people spot if they have missed a supply from a device tree or
> equivalent data structure.
>
> Suggested-by: Stephen Warren <swarren@nvidia.com>
Oh, well I was going to ack it, but I guess there's no point since I
suggested it:-)
prev parent reply other threads:[~2013-10-04 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 10:44 [PATCH] regulator: core: Always warn when using a dummy regulator Mark Brown
2013-10-04 20:59 ` Stephen Warren [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=524F2C43.9070302@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--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