From: kernel test robot <lkp@intel.com>
To: "Johnson CH Chen (陳昭勳)" <JohnsonCH.Chen@moxa.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: kbuild-all@lists.01.org,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
LINUX-WATCHDOG <linux-watchdog@vger.kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] rtc: ds1374: wdt: Use watchdog core for watchdog part
Date: Thu, 2 Jul 2020 20:25:00 +0800 [thread overview]
Message-ID: <202007022056.MNzi5Ly4%lkp@intel.com> (raw)
In-Reply-To: <HK2PR01MB3281311E985BB6ED61B545FDFA6C0@HK2PR01MB3281.apcprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
Hi "Johnson,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on abelloni/rtc-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Johnson-CH-Chen/rtc-ds1374-wdt-Use-watchdog-core-for-watchdog-part/20200701-181230
base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
config: x86_64-randconfig-a015-20200701 (attached as .config)
compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "devm_watchdog_register_device" [drivers/rtc/rtc-ds1374.ko] undefined!
>> ERROR: modpost: "watchdog_init_timeout" [drivers/rtc/rtc-ds1374.ko] undefined!
>> ERROR: modpost: "watchdog_unregister_device" [drivers/rtc/rtc-ds1374.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31996 bytes --]
next prev parent reply other threads:[~2020-07-02 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 10:09 [PATCH] rtc: ds1374: wdt: Use watchdog core for watchdog part Johnson CH Chen (陳昭勳)
2020-07-01 14:05 ` Guenter Roeck
2020-07-03 10:15 ` Johnson CH Chen (陳昭勳)
2020-07-02 12:25 ` kernel test robot [this message]
2020-07-02 14:38 ` kernel test robot
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=202007022056.MNzi5Ly4%lkp@intel.com \
--to=lkp@intel.com \
--cc=JohnsonCH.Chen@moxa.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.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