From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, shuahkhan@gmail.com,
Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH 3.13] regulator: core: Change dummy supplies error message to a warning
Date: Wed, 19 Mar 2014 23:58:28 +0000 [thread overview]
Message-ID: <20140319235828.GC22080@kroah.com> (raw)
In-Reply-To: <1394054987-4743-1-git-send-email-shuah.kh@samsung.com>
On Wed, Mar 05, 2014 at 02:29:47PM -0700, Shuah Khan wrote:
> Change "dummy supplies not allowed" error message to warning instead,
> as this is a just warning message with no change to the behavior.
>
> upstream commit acc3d5cec84f82ebea535fa0bd9500ac3df2aee9
>
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> Signed-off-by: Mark Brown <broonie@linaro.org>
> ---
>
> Back porting as the original patch tagged for stable failed to apply.
> Included Mark Brown's Signed-off from the original commit. This change
> is not applicable to 3.12 and earlier.
>
> drivers/regulator/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> index 0186c1b..804521a 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -1359,7 +1359,7 @@ static struct regulator *_regulator_get(struct device *dev, const char *id,
> rdev = dummy_regulator_rdev;
> goto found;
> } else {
> - dev_err(dev, "dummy supplies not allowed\n");
> + dev_warn(dev, "dummy supplies not allowed\n");
This really isn't a problem that warrents a stable backport, sorry. I
can understand distros being "annoyed" at it, but probably not.
greg k-h
next prev parent reply other threads:[~2014-03-19 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 21:29 [PATCH 3.13] regulator: core: Change dummy supplies error message to a warning Shuah Khan
2014-03-05 22:00 ` Joe Perches
2014-03-05 22:29 ` Shuah Khan
2014-03-19 23:58 ` Greg KH [this message]
2014-03-20 10:02 ` Mark Brown
2014-03-20 21:16 ` Greg KH
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=20140319235828.GC22080@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah.kh@samsung.com \
--cc=shuahkhan@gmail.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).