linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
	Dipen Patel <dipenp@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org, timestamp@lists.linux.dev,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2] gpiolib: don't build HTE code with CONFIG_HTE disabled
Date: Thu, 13 Feb 2025 15:45:59 +0800	[thread overview]
Message-ID: <202502131503.gMZldZLL-lkp@intel.com> (raw)
In-Reply-To: <20250207083146.17872-1-brgl@bgdev.pl>

Hi Bartosz,

kernel test robot noticed the following build errors:

[auto build test ERROR on brgl/gpio/for-next]
[also build test ERROR on linus/master v6.14-rc2 next-20250212]
[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/Bartosz-Golaszewski/gpiolib-don-t-build-HTE-code-with-CONFIG_HTE-disabled/20250207-163408
base:   https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link:    https://lore.kernel.org/r/20250207083146.17872-1-brgl%40bgdev.pl
patch subject: [PATCH v2] gpiolib: don't build HTE code with CONFIG_HTE disabled
config: i386-buildonly-randconfig-001-20250213 (https://download.01.org/0day-ci/archive/20250213/202502131503.gMZldZLL-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250213/202502131503.gMZldZLL-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/202502131503.gMZldZLL-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from drivers/reset/reset-gpio.c:3:
   include/linux/gpio/consumer.h: In function 'gpiod_enable_hw_timestamp_ns':
>> include/linux/gpio/consumer.h:557:17: error: implicit declaration of function 'WARN_ON' [-Werror=implicit-function-declaration]
     557 |                 WARN_ON(desc);
         |                 ^~~~~~~
   include/linux/gpio/consumer.h:559:17: error: 'ENOSYS' undeclared (first use in this function)
     559 |         return -ENOSYS;
         |                 ^~~~~~
   include/linux/gpio/consumer.h:559:17: note: each undeclared identifier is reported only once for each function it appears in
   include/linux/gpio/consumer.h: In function 'gpiod_disable_hw_timestamp_ns':
   include/linux/gpio/consumer.h:567:17: error: 'ENOSYS' undeclared (first use in this function)
     567 |         return -ENOSYS;
         |                 ^~~~~~
   cc1: some warnings being treated as errors


vim +/WARN_ON +557 include/linux/gpio/consumer.h

   548	
   549	#if IS_ENABLED(CONFIG_GPIOLIB) && IS_ENABLED(CONFIG_HTE)
   550	int gpiod_enable_hw_timestamp_ns(struct gpio_desc *desc, unsigned long flags);
   551	int gpiod_disable_hw_timestamp_ns(struct gpio_desc *desc, unsigned long flags);
   552	#else
   553	static inline int gpiod_enable_hw_timestamp_ns(struct gpio_desc *desc,
   554						       unsigned long flags)
   555	{
   556		if (!IS_ENABLED(CONFIG_GPIOLIB))
 > 557			WARN_ON(desc);
   558	
   559		return -ENOSYS;
   560	}
   561	static inline int gpiod_disable_hw_timestamp_ns(struct gpio_desc *desc,
   562							unsigned long flags)
   563	{
   564		if (!IS_ENABLED(CONFIG_GPIOLIB))
   565			WARN_ON(desc);
   566	
   567		return -ENOSYS;
   568	}
   569	#endif /* CONFIG_GPIOLIB && CONFIG_HTE */
   570	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      parent reply	other threads:[~2025-02-13  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07  8:31 [PATCH v2] gpiolib: don't build HTE code with CONFIG_HTE disabled Bartosz Golaszewski
2025-02-07  8:32 ` Bartosz Golaszewski
2025-02-07 20:24 ` kernel test robot
2025-02-13  7:45 ` 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=202502131503.gMZldZLL-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=dipenp@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=timestamp@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).