From: kernel test robot <lkp@intel.com>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
aaro.koskinen@iki.fi, andreas@kemnade.info, khilman@baylibre.com,
rogerq@kernel.org, tony@atomide.com, linus.walleij@linaro.org,
brgl@bgdev.pl, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
m-leonard@ti.com, praneeth@ti.com, jcormier@criticallink.com
Subject: Re: [PATCH v6 2/2] gpio: tps65219: Add support for TI TPS65214 PMIC
Date: Fri, 4 Jul 2025 15:31:09 +0800 [thread overview]
Message-ID: <202507041537.da8R2iEX-lkp@intel.com> (raw)
In-Reply-To: <20250703180751.168755-3-s-ramamoorthy@ti.com>
Hi Shree,
kernel test robot noticed the following build errors:
[auto build test ERROR on v6.16-rc4]
[also build test ERROR on linus/master next-20250703]
[cannot apply to tmlind-omap/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Shree-Ramamoorthy/gpio-tps65219-Update-_IDX-_OFFSET-macro-prefix/20250704-021048
base: v6.16-rc4
patch link: https://lore.kernel.org/r/20250703180751.168755-3-s-ramamoorthy%40ti.com
patch subject: [PATCH v6 2/2] gpio: tps65219: Add support for TI TPS65214 PMIC
config: hexagon-randconfig-002-20250704 (https://download.01.org/0day-ci/archive/20250704/202507041537.da8R2iEX-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 61529d9e36fa86782a2458e6bdeedf7f376ef4b5)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250704/202507041537.da8R2iEX-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/202507041537.da8R2iEX-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpio/gpio-tps65219.c:208:14: error: incompatible function pointer types initializing 'int (*)(struct gpio_chip *, unsigned int, int)' with an expression of type 'void (struct gpio_chip *, unsigned int, int)' [-Wincompatible-function-pointer-types]
208 | .set_rv = tps65219_gpio_set,
| ^~~~~~~~~~~~~~~~~
drivers/gpio/gpio-tps65219.c:221:14: error: incompatible function pointer types initializing 'int (*)(struct gpio_chip *, unsigned int, int)' with an expression of type 'void (struct gpio_chip *, unsigned int, int)' [-Wincompatible-function-pointer-types]
221 | .set_rv = tps65219_gpio_set,
| ^~~~~~~~~~~~~~~~~
2 errors generated.
vim +208 drivers/gpio/gpio-tps65219.c
200
201 static const struct gpio_chip tps65214_template_chip = {
202 .label = "tps65214-gpio",
203 .owner = THIS_MODULE,
204 .get_direction = tps65214_gpio_get_direction,
205 .direction_input = tps65219_gpio_direction_input,
206 .direction_output = tps65219_gpio_direction_output,
207 .get = tps65219_gpio_get,
> 208 .set_rv = tps65219_gpio_set,
209 .base = -1,
210 .ngpio = 2,
211 .can_sleep = true,
212 };
213
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-07-04 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 18:07 [PATCH v6 0/2] Add TI TPS65214 PMIC GPIO Support Shree Ramamoorthy
2025-07-03 18:07 ` [PATCH v6 1/2] gpio: tps65219: Update _IDX & _OFFSET macro prefix Shree Ramamoorthy
2025-07-03 18:07 ` [PATCH v6 2/2] gpio: tps65219: Add support for TI TPS65214 PMIC Shree Ramamoorthy
2025-07-03 19:05 ` Christophe JAILLET
2025-07-03 20:13 ` Shree Ramamoorthy
2025-07-04 7:31 ` kernel test robot [this message]
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=202507041537.da8R2iEX-lkp@intel.com \
--to=lkp@intel.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=brgl@bgdev.pl \
--cc=jcormier@criticallink.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=m-leonard@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®