From: kernel test robot <lkp@intel.com>
To: Steve Wahl <steve.wahl@hpe.com>,
Craig Lamparter <craig.lamparter@hpe.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Russ Anderson <rja@hpe.com>,
Dimitri Sivanich <sivanich@hpe.com>,
Kyle Meyer <kyle.meyer@hpe.com>,
Keng-Yu Lin <keng-yu.lin@hpe.com>,
Collins@owl.eag.rdlabs.hpecorp.net
Subject: Re: [PATCH] Refine hpwdt message for UV platform
Date: Wed, 8 Apr 2026 04:33:21 +0800 [thread overview]
Message-ID: <202604080401.igdhwsPk-lkp@intel.com> (raw)
In-Reply-To: <20260316214530.104344-1-steve.wahl@hpe.com>
Hi Steve,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.0-rc7 next-20260406]
[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/Steve-Wahl/Refine-hpwdt-message-for-UV-platform/20260317-060404
base: linus/master
patch link: https://lore.kernel.org/r/20260316214530.104344-1-steve.wahl%40hpe.com
patch subject: [PATCH] Refine hpwdt message for UV platform
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20260408/202604080401.igdhwsPk-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260408/202604080401.igdhwsPk-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/202604080401.igdhwsPk-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/watchdog/hpwdt.c:28:10: fatal error: asm/uv/uv.h: No such file or directory
28 | #include <asm/uv/uv.h>
| ^~~~~~~~~~~~~
compilation terminated.
vim +28 drivers/watchdog/hpwdt.c
13
14 #include <linux/device.h>
15 #include <linux/hex.h>
16 #include <linux/io.h>
17 #include <linux/kernel.h>
18 #include <linux/module.h>
19 #include <linux/moduleparam.h>
20 #include <linux/pci.h>
21 #include <linux/pci_ids.h>
22 #include <linux/types.h>
23 #include <linux/watchdog.h>
24 #ifdef CONFIG_HPWDT_NMI_DECODING
25 #include <asm/nmi.h>
26 #endif
27 #include <linux/crash_dump.h>
> 28 #include <asm/uv/uv.h>
29
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-04-07 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 21:45 [PATCH] Refine hpwdt message for UV platform Steve Wahl
2026-03-17 18:38 ` Guenter Roeck
2026-03-17 18:39 ` Guenter Roeck
2026-04-07 20:33 ` kernel test robot [this message]
2026-04-07 21:08 ` Steve Wahl
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=202604080401.igdhwsPk-lkp@intel.com \
--to=lkp@intel.com \
--cc=Collins@owl.eag.rdlabs.hpecorp.net \
--cc=craig.lamparter@hpe.com \
--cc=keng-yu.lin@hpe.com \
--cc=kyle.meyer@hpe.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=rja@hpe.com \
--cc=sivanich@hpe.com \
--cc=steve.wahl@hpe.com \
--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