linux-kernel - Re: [PATCH] clk: pxa: Use __iomem properly and staticize lock variable

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: <20161109204331.GU16026@codeaurora.org>
Date:   Wed, 9 Nov 2016 12:43:31 -0800
From:   Stephen Boyd <sboyd@...eaurora.org>
To:     Michael Turquette <mturquette@...libre.com>
Cc:     linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
        Robert Jarzmik <robert.jarzmik@...e.fr>
Subject: Re: [PATCH] clk: pxa: Use __iomem properly and staticize lock
 variable

On 11/08, Stephen Boyd wrote:
> This function is passed an __iomem pointer but we use a u32
> pointer instead which makes checkers like spare complain.
> Furthermore, "lock" is a pretty poor variable name for a string
> that will go into lockdep reports and the symbol isn't marked
> static. Cleanup all this.
> 
> Cc: Robert Jarzmik <robert.jarzmik@...e.fr>
> Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
> ---

Applied to clk-next

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project