linux-kernel - Re: [PATCH] gpio: syscon: reduce message level when direction reg offset not in dt

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]

Date:	Tue, 24 Mar 2015 13:52:10 -0700
From:	santosh shilimkar <santosh.shilimkar@...cle.com>
To:	grygorii.strashko@...aro.org, linux@....linux.org.uk,
	Linus Walleij <linus.walleij@...aro.org>,
	Alexandre Courbot <gnurou@...il.com>
CC:	m-karicheri2@...com, ssantosh@...nel.org,
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gpio: syscon: reduce message level when direction reg
 offset not in dt

On 3/24/2015 11:42 AM, grygorii.strashko@...aro.org wrote:
> From: Grygorii Strashko <grygorii.strashko@...aro.org>
>
> Now GPIO syscon driver produces bunch of warnings during the
> boot of Kesytone 2 SoCs:
>   gpio-syscon soc:keystone_dsp_gpio@...20240: can't read the dir register offset!
>   gpio-syscon soc:keystone_dsp_gpio@...0244: can't read the dir register offset!
>
> This message unintentionally was added using dev_err(), but its
> actual log level is debug, because third cell of "ti,syscon-dev" is
> optional.
>
> Hence change it to dev_dbg() as it should be.
>
> This patch fixes commit:
>   5a3e3f8 ("gpio: syscon: retriave syscon node and regs offsets from dt")
>
> Reported-by: Russell King <linux@....linux.org.uk>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@...aro.org>
> ---
Acked-by: Santosh Shilimkar <ssantosh@...nel.org>
--
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/