lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140319235828.GC22080@kroah.com>
Date:	Wed, 19 Mar 2014 23:58:28 +0000
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Shuah Khan <shuah.kh@...sung.com>
Cc:	lgirdwood@...il.com, broonie@...nel.org, stable@...r.kernel.org,
	linux-kernel@...r.kernel.org, shuahkhan@...il.com,
	Mark Brown <broonie@...aro.org>
Subject: Re: [PATCH 3.13] regulator: core: Change dummy supplies error
 message to a warning

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@...sung.com>
> Signed-off-by: Mark Brown <broonie@...aro.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ