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-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[pinctrl:devel 30/37] drivers/pinctrl/pinconf.c:205:6: sparse: symbol 'pinconf_show_config' was not declared. Should it be static?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: [pinctrl:devel 30/37] drivers/pinctrl/pinconf.c:205:6: sparse: symbol 'pinconf_show_config' was not declared. Should it be static?
- From: kbuild test robot <fengguang.wu@xxxxxxxxx>
- Date: Fri, 17 Jul 2015 21:37:09 +0800
- User-agent: Mutt/1.5.23 (2014-03-12)
- Follow-Ups:
- [PATCH pinctrl] pinctrl: pinconf: pinconf_show_config() can be static
- From: kbuild test robot
- [PATCH pinctrl] pinctrl: pinconf: pinconf_show_config() can be static
- Prev by Date: [PATCH pinctrl] pinctrl: pinconf: pinconf_show_config() can be static
- Next by Date: Re: [PATCH pinctrl] pinctrl: pinconf: pinconf_show_config() can be static
- Previous by thread: [GIT PULL] GPIO fixes for v4.2 take one
- Next by thread: [PATCH pinctrl] pinctrl: pinconf: pinconf_show_config() can be static
- Index(es):
 |