From: kbuild test robot <lkp@intel.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: kbuild-all@01.org, linux-hwmon@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>
Subject: [hwmon:watchdog-next 57/71] jz4740_wdt.c:(.text.jz4740_wdt_stop+0x28): undefined reference to `jz4740_timer_disable_watchdog'
Date: Fri, 21 Jun 2019 04:08:11 +0800 [thread overview]
Message-ID: <201906210410.0uMwILcJ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git watchdog-next
head: ae399280879b77d63433860b54e00fdf8212df21
commit: b0225022beeb34df00bbf0eea25a2ed537629ac2 [57/71] watchdog: jz4740: Drop dependency on MACH_JZ47xx
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout b0225022beeb34df00bbf0eea25a2ed537629ac2
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/watchdog/jz4740_wdt.o: In function `jz4740_wdt_stop':
>> jz4740_wdt.c:(.text.jz4740_wdt_stop+0x28): undefined reference to `jz4740_timer_disable_watchdog'
drivers/watchdog/jz4740_wdt.o: In function `jz4740_wdt_start':
>> jz4740_wdt.c:(.text.jz4740_wdt_start+0x3c): undefined reference to `jz4740_timer_enable_watchdog'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 60937 bytes --]
reply other threads:[~2019-06-20 20:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201906210410.0uMwILcJ%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=paul@crapouillou.net \
/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;
as well as URLs for NNTP newsgroup(s).