From: kernel test robot <lkp@intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org
Subject: [brgl:gpio/devel 36/62] include/linux/pinctrl/consumer.h:76:1: error: conflicting types for 'pinctrl_gpio_can_use_line'; have 'bool(struct gpio_chip *, unsigned int)' {aka '_Bool(struct gpio_chip *, unsigned int)'}
Date: Fri, 13 Oct 2023 02:46:23 +0800 [thread overview]
Message-ID: <202310130237.2NLTLV30-lkp@intel.com> (raw)
Hi Bartosz,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/devel
head: f45ee006d473c033a7d0152b182f9ba12cf52ce5
commit: c193f038b53221830113a2ef53a30f12d22e31e8 [36/62] treewide: rename pinctrl_gpio_can_use_line_new()
config: s390-randconfig-001-20231013 (https://download.01.org/0day-ci/archive/20231013/202310130237.2NLTLV30-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231013/202310130237.2NLTLV30-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310130237.2NLTLV30-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/i2c/i2c-core-base.c:36:
>> include/linux/pinctrl/consumer.h:76:1: error: conflicting types for 'pinctrl_gpio_can_use_line'; have 'bool(struct gpio_chip *, unsigned int)' {aka '_Bool(struct gpio_chip *, unsigned int)'}
76 | pinctrl_gpio_can_use_line(struct gpio_chip *gc, unsigned int offset)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/pinctrl/consumer.h:70:20: note: previous definition of 'pinctrl_gpio_can_use_line' with type 'bool(unsigned int)' {aka '_Bool(unsigned int)'}
70 | static inline bool pinctrl_gpio_can_use_line(unsigned gpio)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +76 include/linux/pinctrl/consumer.h
74
75 static inline bool
> 76 pinctrl_gpio_can_use_line(struct gpio_chip *gc, unsigned int offset)
77 {
78 return true;
79 }
80
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-12 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202310130237.2NLTLV30-lkp@intel.com \
--to=lkp@intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).