linux-kernel - Re: [PATCH -next] regulator: Make symbols static

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: <27596178-6321-738c-18ed-c8bddb7c3ff4@huawei.com>
Date:   Sat, 20 Apr 2019 11:13:23 +0800
From:   YueHaibing <yuehaibing@...wei.com>
To:     Mark Brown <broonie@...nel.org>
CC:     <lgirdwood@...il.com>, <mcoquelin.stm32@...il.com>,
        <alexandre.torgue@...com>, <linux-kernel@...r.kernel.org>,
        <linux-stm32@...md-mailman.stormreply.com>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH -next] regulator: Make symbols static

On 2019/4/20 0:12, Mark Brown wrote:
> On Tue, Apr 16, 2019 at 10:41:09PM +0800, Yue Haibing wrote:
>> From: YueHaibing <yuehaibing@...wei.com>
>>
>> Fix sparse warnings:
>>
>> drivers/regulator/stm32-pwr.c:35:5: warning:
>>  symbol 'ready_mask_table' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:47:5: warning:
>>  symbol 'stm32_pwr_reg_is_ready' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:57:5: warning:
>>  symbol 'stm32_pwr_reg_is_enabled' was not declared. Should it be static?
> 
> This doesn't apply against current code, please check and resend (I
> think it's just that someone else made similar fixes already but didn't
> check properly).

Yep, there is already a fix from kbuild test robot:

82f26185a912 ("regulator: ready_mask_table[] can be static")

>