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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 6 Sep 2022 18:02:22 +0000
From:   <Kumaravel.Thiagarajan@...rochip.com>
To:     <lkp@...el.com>
CC:     <kbuild-all@...ts.01.org>, <linux-kernel@...r.kernel.org>,
        <gregkh@...uxfoundation.org>
Subject: RE: [char-misc:char-misc-next 21/24]
 drivers/misc/mchp_pci1xxxx/mchp_pci1xxxx_gpio.c:135:34: sparse: sparse:
 symbol 'pci1xxxx_gpio_auxiliary_id_table' was not declared. Should it be
 static?

> -----Original Message-----
> From: kernel test robot <lkp@...el.com>
> Sent: Monday, September 5, 2022 12:07 PM
> To: Kumaravel Thiagarajan - I21417 <Kumaravel.Thiagarajan@...rochip.com>
> Cc: kbuild-all@...ts.01.org; linux-kernel@...r.kernel.org; Greg Kroah-
> Hartman <gregkh@...uxfoundation.org>
> Subject: [char-misc:char-misc-next 21/24]
> drivers/misc/mchp_pci1xxxx/mchp_pci1xxxx_gpio.c:135:34: sparse: sparse:
> symbol 'pci1xxxx_gpio_auxiliary_id_table' was not declared. Should it be
> static?
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> char-misc-next
> head:   50e177c5bfd9abc3828cb57e14e6169170f6764a
> commit: 7d3e4d807df2a216b9aa2944372f2b3f6ef3f205 [21/24] misc:
> microchip: pci1xxxx: load gpio driver for the gpio controller auxiliary device
> enumerated by the auxiliary bus driver.
> config: i386-randconfig-s033-20220905
> compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
.
.
.
> 
> sparse warnings: (new ones prefixed by >>)
> >> drivers/misc/mchp_pci1xxxx/mchp_pci1xxxx_gpio.c:135:34: sparse:
> sparse: symbol 'pci1xxxx_gpio_auxiliary_id_table' was not declared. Should it
> be static?
Greg, do I need to submit another patch to resolve this warning on char-misc-next?
I did not combine this with the last patch thinking that the last patch would
be merged with the commit that introduced the errors and not queued.

Thank You.

Regards,
Kumaravel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ