From: kernel test robot <lkp@intel.com>
To: Rosen Penev <rosenp@gmail.com>, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] gpio: sodaville: allow COMPILE_TEST builds
Date: Tue, 12 May 2026 19:42:28 +0800 [thread overview]
Message-ID: <202605121902.NsjonizV-lkp@intel.com> (raw)
In-Reply-To: <20260509003327.955942-1-rosenp@gmail.com>
Hi Rosen,
kernel test robot noticed the following build errors:
[auto build test ERROR on brgl/gpio/for-next]
[also build test ERROR on linus/master v7.1-rc3 next-20260508]
[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/Rosen-Penev/gpio-sodaville-allow-COMPILE_TEST-builds/20260512-125042
base: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link: https://lore.kernel.org/r/20260509003327.955942-1-rosenp%40gmail.com
patch subject: [PATCH] gpio: sodaville: allow COMPILE_TEST builds
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260512/202605121902.NsjonizV-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260512/202605121902.NsjonizV-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/202605121902.NsjonizV-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpio/gpio-sodaville.c:253:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
253 | builtin_pci_driver(sdv_gpio_driver);
| ^
| int
>> drivers/gpio/gpio-sodaville.c:253:20: error: a parameter list without types is only allowed in a function definition
253 | builtin_pci_driver(sdv_gpio_driver);
| ^
2 errors generated.
vim +/int +253 drivers/gpio/gpio-sodaville.c
b43ab901d671e3 Sebastian Andrzej Siewior 2011-06-27 244
b43ab901d671e3 Sebastian Andrzej Siewior 2011-06-27 245 static struct pci_driver sdv_gpio_driver = {
6a5ead91d45d09 Paul Gortmaker 2016-05-09 246 .driver = {
6a5ead91d45d09 Paul Gortmaker 2016-05-09 247 .suppress_bind_attrs = true,
6a5ead91d45d09 Paul Gortmaker 2016-05-09 248 },
b43ab901d671e3 Sebastian Andrzej Siewior 2011-06-27 249 .name = DRV_NAME,
b43ab901d671e3 Sebastian Andrzej Siewior 2011-06-27 250 .id_table = sdv_gpio_pci_ids,
b43ab901d671e3 Sebastian Andrzej Siewior 2011-06-27 251 .probe = sdv_gpio_probe,
b43ab901d671e3 Sebastian Andrzej Siewior 2011-06-27 252 };
6a5ead91d45d09 Paul Gortmaker 2016-05-09 @253 builtin_pci_driver(sdv_gpio_driver);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-05-12 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 0:33 [PATCH] gpio: sodaville: allow COMPILE_TEST builds Rosen Penev
2026-05-11 10:15 ` Bartosz Golaszewski
2026-05-12 11:09 ` kernel test robot
2026-05-12 11:42 ` 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=202605121902.NsjonizV-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=rosenp@gmail.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