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: <0ACAE736BB7A70499F1D8D5E6AC1854C01BDDAEA40@NB-EX-MBX01.diasemi.com>
Date:	Tue, 24 Feb 2015 00:51:49 +0000
From:	"Opensource [James Seong-Won Ban]" <James.Ban.opensource@...semi.com>
To:	Geert Uytterhoeven <geert+renesas@...der.be>,
	Support Opensource <Support.Opensource@...semi.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	"Mark Brown" <broonie@...nel.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] regulator: da9211: Fix wrong register name in error
 message

On February 24, 2015 1:11, Geert Uytterhoeven wrote:

> We tried to read the CONFIG_E register, not the CONTROL_E register.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
>  drivers/regulator/da9211-regulator.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/regulator/da9211-regulator.c b/drivers/regulator/da9211-
> regulator.c
> index 01343419555ee336..3eda2dd577137f2a 100644
> --- a/drivers/regulator/da9211-regulator.c
> +++ b/drivers/regulator/da9211-regulator.c
> @@ -344,7 +344,7 @@ static int da9211_regulator_init(struct da9211 *chip)
> 
>  	ret = regmap_read(chip->regmap, DA9211_REG_CONFIG_E, &data);
>  	if (ret < 0) {
> -		dev_err(chip->dev, "Failed to read CONTROL_E reg: %d\n", ret);
> +		dev_err(chip->dev, "Failed to read CONFIG_E reg: %d\n", ret);
>  		return ret;
>  	}
> 
> --
> 1.9.1
Acked-by: James Ban <james.ban.opensource@...semi.com>
--
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