All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [groeck-staging:hwmon-next 18/32] drivers/hwmon/hwmon.c:344:13: error: redefinition of 'is_hwmon_device'
Date: Mon, 31 Aug 2026 06:22:09 +0200	[thread overview]
Message-ID: <202608310650.HNAE53Na-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
head:   6d28113b5ea75542b72d9f73ab9aaf0d0a49a104
commit: 40b20f8e6b53ea701f250fe2d3cac82e07c18468 [18/32] hwmon: Ensure that 'dev' passed to hwmon_notify_event() is a hwmon device
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260831/202608310650.HNAE53Na-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260831/202608310650.HNAE53Na-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/202608310650.HNAE53Na-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/hwmon/hwmon.c:344:13: error: redefinition of 'is_hwmon_device'
     344 | static bool is_hwmon_device(struct device *dev)
         |             ^
   drivers/hwmon/hwmon.c:321:13: note: previous definition is here
     321 | static bool is_hwmon_device(struct device *dev)
         |             ^
   1 error generated.


vim +/is_hwmon_device +344 drivers/hwmon/hwmon.c

   327	
   328	/*
   329	 * PEC support
   330	 *
   331	 * The 'pec' attribute is attached to I2C client devices. It is only provided
   332	 * if the i2c controller supports PEC.
   333	 *
   334	 * The mutex ensures that PEC configuration between i2c device and the hardware
   335	 * is consistent. Use a single mutex because attribute writes are supposed to be
   336	 * rare, and maintaining a separate mutex for each hardware monitoring device
   337	 * would add substantial complexity to the driver for little if any gain.
   338	 *
   339	 * The hardware monitoring device is identified as child of the i2c client
   340	 * device. This assumes that only a single hardware monitoring device is
   341	 * attached to an i2c client device.
   342	 */
   343	
 > 344	static bool is_hwmon_device(struct device *dev)
   345	{
   346		return is_hwmon_device(dev);
   347	}
   348	

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

                 reply	other threads:[~2026-08-31  4:22 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=202608310650.HNAE53Na-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux@roeck-us.net \
    --cc=llvm@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.