public inbox for linux-watchdog@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v2 1/1] watchdog: Don't use "proxy" headers
Date: Mon, 7 Jul 2025 06:13:52 +0800	[thread overview]
Message-ID: <202507070407.CE8Utfgk-lkp@intel.com> (raw)
In-Reply-To: <20250627073753.589509-1-andriy.shevchenko@linux.intel.com>

Hi Andy,

kernel test robot noticed the following build errors:

[auto build test ERROR on groeck-staging/hwmon-next]
[also build test ERROR on linus/master v6.16-rc4 next-20250704]
[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/Andy-Shevchenko/watchdog-Don-t-use-proxy-headers/20250627-153933
base:   https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
patch link:    https://lore.kernel.org/r/20250627073753.589509-1-andriy.shevchenko%40linux.intel.com
patch subject: [PATCH v2 1/1] watchdog: Don't use "proxy" headers
config: i386-randconfig-052-20250706 (https://download.01.org/0day-ci/archive/20250707/202507070407.CE8Utfgk-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250707/202507070407.CE8Utfgk-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/202507070407.CE8Utfgk-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/watchdog/it87_wdt.c: In function 'superio_enter':
>> drivers/watchdog/it87_wdt.c:121:14: error: implicit declaration of function 'request_muxed_region' [-Werror=implicit-function-declaration]
     121 |         if (!request_muxed_region(REG, 2, WATCHDOG_NAME))
         |              ^~~~~~~~~~~~~~~~~~~~
   drivers/watchdog/it87_wdt.c: In function 'superio_exit':
>> drivers/watchdog/it87_wdt.c:135:9: error: implicit declaration of function 'release_region' [-Werror=implicit-function-declaration]
     135 |         release_region(REG, 2);
         |         ^~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/request_muxed_region +121 drivers/watchdog/it87_wdt.c

e1fee94f346387 Oliver Schuster 2008-03-05  115  
a134b825608df6 Nat Gurumoorthy 2011-05-09  116  static inline int superio_enter(void)
e1fee94f346387 Oliver Schuster 2008-03-05  117  {
a134b825608df6 Nat Gurumoorthy 2011-05-09  118  	/*
a134b825608df6 Nat Gurumoorthy 2011-05-09  119  	 * Try to reserve REG and REG + 1 for exclusive access.
a134b825608df6 Nat Gurumoorthy 2011-05-09  120  	 */
a134b825608df6 Nat Gurumoorthy 2011-05-09 @121  	if (!request_muxed_region(REG, 2, WATCHDOG_NAME))
a134b825608df6 Nat Gurumoorthy 2011-05-09  122  		return -EBUSY;
a134b825608df6 Nat Gurumoorthy 2011-05-09  123  
e1fee94f346387 Oliver Schuster 2008-03-05  124  	outb(0x87, REG);
e1fee94f346387 Oliver Schuster 2008-03-05  125  	outb(0x01, REG);
e1fee94f346387 Oliver Schuster 2008-03-05  126  	outb(0x55, REG);
e1fee94f346387 Oliver Schuster 2008-03-05  127  	outb(0x55, REG);
a134b825608df6 Nat Gurumoorthy 2011-05-09  128  	return 0;
e1fee94f346387 Oliver Schuster 2008-03-05  129  }
e1fee94f346387 Oliver Schuster 2008-03-05  130  
e1fee94f346387 Oliver Schuster 2008-03-05  131  static inline void superio_exit(void)
e1fee94f346387 Oliver Schuster 2008-03-05  132  {
e1fee94f346387 Oliver Schuster 2008-03-05  133  	outb(0x02, REG);
e1fee94f346387 Oliver Schuster 2008-03-05  134  	outb(0x02, VAL);
a134b825608df6 Nat Gurumoorthy 2011-05-09 @135  	release_region(REG, 2);
e1fee94f346387 Oliver Schuster 2008-03-05  136  }
e1fee94f346387 Oliver Schuster 2008-03-05  137  

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

  reply	other threads:[~2025-07-06 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  7:37 [PATCH v2 1/1] watchdog: Don't use "proxy" headers Andy Shevchenko
2025-07-06 22:13 ` kernel test robot [this message]
2025-07-07 15:20 ` Guenter Roeck

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=202507070407.CE8Utfgk-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=wim@linux-watchdog.org \
    /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