From: kernel test robot <lkp@intel.com>
To: Wolfram Sang <wsa-dev@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Wolfram Sang <wsa-dev@sang-engineering.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 2/2] watchdog: renesas_wwdt: add driver
Date: Thu, 18 Sep 2025 22:22:04 +0800 [thread overview]
Message-ID: <202509182204.LwGhKzRi-lkp@intel.com> (raw)
In-Reply-To: <20250917185651.12428-3-wsa+renesas@sang-engineering.com>
Hi Wolfram,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on groeck-staging/hwmon-next linus/master v6.17-rc6 next-20250917]
[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/Wolfram-Sang/dt-bindings-watchdog-Add-Renesas-WWDT/20250918-070043
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20250917185651.12428-3-wsa%2Brenesas%40sang-engineering.com
patch subject: [PATCH 2/2] watchdog: renesas_wwdt: add driver
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20250918/202509182204.LwGhKzRi-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250918/202509182204.LwGhKzRi-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/202509182204.LwGhKzRi-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/watchdog/renesas_wwdt.c: In function 'wwdt_probe':
>> drivers/watchdog/renesas_wwdt.c:20:25: error: implicit declaration of function 'FIELD_GET' [-Wimplicit-function-declaration]
20 | #define WDTA0OVF(x) FIELD_GET(GENMASK(6, 4), x)
| ^~~~~~~~~
drivers/watchdog/renesas_wwdt.c:98:30: note: in expansion of macro 'WDTA0OVF'
98 | interval = 1 << (9 + WDTA0OVF(val));
| ^~~~~~~~
vim +/FIELD_GET +20 drivers/watchdog/renesas_wwdt.c
18
19 #define WDTA0MD 0x0c
> 20 #define WDTA0OVF(x) FIELD_GET(GENMASK(6, 4), x)
21 #define WDTA0WIE BIT(3)
22 #define WDTA0ERM BIT(2)
23 #define WDTA0WS(x) FIELD_GET(GENMASK(1, 0), x)
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-18 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 18:56 [PATCH 0/2] watchdog: add Renesas Window Watchdog support Wolfram Sang
2025-09-17 18:56 ` [PATCH 1/2] dt-bindings: watchdog: Add Renesas WWDT Wolfram Sang
2025-09-17 19:16 ` Conor Dooley
2025-09-17 18:56 ` [PATCH 2/2] watchdog: renesas_wwdt: add driver Wolfram Sang
2025-09-18 14:22 ` kernel test robot [this message]
2025-10-06 11:58 ` Geert Uytterhoeven
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=202509182204.LwGhKzRi-lkp@intel.com \
--to=lkp@intel.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=magnus.damm@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wim@linux-watchdog.org \
--cc=wsa-dev@sang-engineering.com \
/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