linux-kernel - Re: [PATCH -next] crypto: ccree

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: <20190503044756.smqzlnluizomtcbw@gondor.apana.org.au>
Date:   Fri, 3 May 2019 12:47:56 +0800
From:   Herbert Xu <herbert@...dor.apana.org.au>
To:     Gilad Ben-Yossef <gilad@...yossef.com>
Cc:     Yue Haibing <yuehaibing@...wei.com>,
        Linux kernel mailing list <linux-kernel@...r.kernel.org>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        kbuild test robot <lkp@...el.com>
Subject: Re: [PATCH -next] crypto: ccree - Make cc_sec_disable static

On Sun, Apr 28, 2019 at 10:56:51AM +0300, Gilad Ben-Yossef wrote:
> On Fri, Apr 26, 2019 at 7:43 PM Yue Haibing <yuehaibing@...wei.com> wrote:
> >
> > From: YueHaibing <yuehaibing@...wei.com>
> >
> > Fix sparse warning:
> >
> > drivers/crypto/ccree/cc_driver.c:37:6: warning:
> >  symbol 'cc_sec_disable' was not declared. Should it be static?
> >
> > Signed-off-by: YueHaibing <yuehaibing@...wei.com>
> 
> Thank you!
> 
> The kbuit test robot already sent the same fix, which I acked.
> It's hard competing with the bots... :-)

For some reason the robot's patch didn't make it into patchwork
so I'm going to take this one instead.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt