From: kernel test robot <lkp@intel.com>
To: minyard@acm.org, im Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: oe-kbuild-all@lists.linux.dev,
openipmi-developer@lists.sourceforge.net,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH] watchdog: Add an IPMI watchdog driver in the watchdog framework
Date: Wed, 3 May 2023 04:42:24 +0800 [thread overview]
Message-ID: <202305030442.Ug9opjA1-lkp@intel.com> (raw)
In-Reply-To: <20230502150215.1266526-1-minyard@acm.org>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on cminyard-ipmi/for-next]
[also build test WARNING on groeck-staging/hwmon-next linus/master v6.3 next-20230428]
[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/minyard-acm-org/watchdog-Add-an-IPMI-watchdog-driver-in-the-watchdog-framework/20230502-230545
base: https://github.com/cminyard/linux-ipmi for-next
patch link: https://lore.kernel.org/r/20230502150215.1266526-1-minyard%40acm.org
patch subject: [PATCH] watchdog: Add an IPMI watchdog driver in the watchdog framework
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20230503/202305030442.Ug9opjA1-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/3138708f587acacac7e95f3098e7a9587866a66e
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review minyard-acm-org/watchdog-Add-an-IPMI-watchdog-driver-in-the-watchdog-framework/20230502-230545
git checkout 3138708f587acacac7e95f3098e7a9587866a66e
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/watchdog/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202305030442.Ug9opjA1-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/watchdog/ipmi_wdt.c:515:5: warning: no previous prototype for 'ipmi_wdt_start' [-Wmissing-prototypes]
515 | int ipmi_wdt_start(struct watchdog_device *wd)
| ^~~~~~~~~~~~~~
drivers/watchdog/ipmi_wdt.c:529:5: warning: no previous prototype for 'ipmi_wdt_stop' [-Wmissing-prototypes]
529 | int ipmi_wdt_stop(struct watchdog_device *wd)
| ^~~~~~~~~~~~~
drivers/watchdog/ipmi_wdt.c:539:5: warning: no previous prototype for 'ipmi_wdt_ping' [-Wmissing-prototypes]
539 | int ipmi_wdt_ping(struct watchdog_device *wd)
| ^~~~~~~~~~~~~
drivers/watchdog/ipmi_wdt.c:550:5: warning: no previous prototype for 'ipmi_wdt_set_timeout' [-Wmissing-prototypes]
550 | int ipmi_wdt_set_timeout(struct watchdog_device *wd, unsigned int to)
| ^~~~~~~~~~~~~~~~~~~~
>> drivers/watchdog/ipmi_wdt.c:563:5: warning: no previous prototype for 'ipmi_wdt_set_pretimeout' [-Wmissing-prototypes]
563 | int ipmi_wdt_set_pretimeout(struct watchdog_device *wd, unsigned int pto)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/ipmi_wdt_set_pretimeout +563 drivers/watchdog/ipmi_wdt.c
561
562 #ifdef HAVE_DIE_NMI
> 563 int ipmi_wdt_set_pretimeout(struct watchdog_device *wd, unsigned int pto)
564 {
565 int rv;
566
567 mutex_lock(&ipmi_watchdog_mutex);
568 pretimeout = pto;
569 if (pto)
570 pretimeout_state = WDOG_PRETIMEOUT_NMI;
571 else
572 pretimeout_state = WDOG_PRETIMEOUT_NONE;
573
574 rv = _ipmi_set_timeout(IPMI_SET_TIMEOUT_HB_IF_NECESSARY);
575 mutex_unlock(&ipmi_watchdog_mutex);
576
577 return rv;
578 }
579 #endif
580
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-05-02 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 15:02 [PATCH] watchdog: Add an IPMI watchdog driver in the watchdog framework minyard
2023-05-02 19:30 ` kernel test robot
2023-05-02 20: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=202305030442.Ug9opjA1-lkp@intel.com \
--to=lkp@intel.com \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=minyard@acm.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=openipmi-developer@lists.sourceforge.net \
--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