linux-kernel - Re: [PATCH] regulator: qcom_rpm: Don't explicitly initialise the first field of config

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] [day] [month] [year] [list]

Message-ID: <20140926082846.GC27755@sirena.org.uk>
Date:	Fri, 26 Sep 2014 09:28:46 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Axel Lin <axel.lin@...ics.com>
Cc:	Bjorn Andersson <bjorn.andersson@...ymobile.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: qcom_rpm: Don't explicitly initialise the
 first field of config

On Wed, Sep 24, 2014 at 05:45:25PM +0800, Axel Lin wrote:
> Doing so generates a warning as the first field is a pointer but we use
> 0 to initialize it.

Applied, thanks.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)