linux-kernel - [pinctrl:devel 30/37] drivers/pinctrl/pinconf.c:205:6: sparse: symbol 'pinconf_show_config' was not declared. Should it be 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-next>] [day] [month] [year] [list]

Message-ID: <201507172143.e7QtgNrM%fengguang.wu@intel.com>
Date:	Fri, 17 Jul 2015 21:37:09 +0800
From:	kbuild test robot <fengguang.wu@...el.com>
To:	Jon Hunter <jonathanh@...dia.com>
Cc:	kbuild-all@...org, Linus Walleij <linus.walleij@...aro.org>,
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [pinctrl:devel 30/37] drivers/pinctrl/pinconf.c:205:6: sparse:
 symbol 'pinconf_show_config' was not declared. Should it be static?

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
head:   16c06171faa4ad430393ca896fc62eb9e2e6dd40
commit: d96310aeddc692cf1f06861cf722c4843e0a3f28 [30/37] pinctrl: pinconf: Fix display of configs
reproduce:
  # apt-get install sparse
  git checkout d96310aeddc692cf1f06861cf722c4843e0a3f28
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/pinctrl/pinconf.c:205:6: sparse: symbol 'pinconf_show_config' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/