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
| ||
|
Date: Thu, 21 Sep 2017 13:37:16 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Colin King <colin.king@...onical.com> Cc: "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, Daniel Drake <drake@...lessm.com>, kernel-janitors@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH][pinctrl-next] pinctrl/amd: make functions amd_gpio_suspend and amd_gpio_resume static On Wed, Sep 13, 2017 at 6:15 PM, Colin King <colin.king@...onical.com> wrote: > From: Colin Ian King <colin.king@...onical.com> > > The functions amd_gpio_suspend and amd_gpio_resume are local to the > source and do not need to be in global scope, so make them static. > > Cleans up sparse warnings: > symbol 'amd_gpio_suspend' was not declared. Should it be static? > symbol 'amd_gpio_resume' was not declared. Should it be static? > > Signed-off-by: Colin Ian King <colin.king@...onical.com> Patch applied with Daniel's review tag. Yours, Linus Walleij
Powered by blists - more mailing lists