From: kbuild test robot <lkp@intel.com>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Matti Vaittinen <mazziesaccount@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>
Subject: drivers/rtc/rtc-bd70528.c:365: undefined reference to `bd70528_wdt_lock'
Date: Thu, 8 Aug 2019 00:56:37 +0800 [thread overview]
Message-ID: <201908080032.EH17lRAx%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]
Hi Matti,
FYI, the error/warning still remains.
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 33920f1ec5bf47c5c0a1d2113989bdd9dfb3fae9
commit: 32a4a4ebf76848828d67f519d07af9eadb6e8300 rtc: bd70528: Initial support for ROHM bd70528 RTC
date: 6 weeks ago
config: x86_64-randconfig-s0-201930 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
git checkout 32a4a4ebf76848828d67f519d07af9eadb6e8300
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/rtc/rtc-bd70528.o: in function `bd70528_alm_enable':
>> drivers/rtc/rtc-bd70528.c:365: undefined reference to `bd70528_wdt_lock'
>> ld: drivers/rtc/rtc-bd70528.c:377: undefined reference to `bd70528_wdt_unlock'
ld: drivers/rtc/rtc-bd70528.o: in function `bd70528_set_rtc_based_timers':
>> drivers/rtc/rtc-bd70528.c:126: undefined reference to `bd70528_wdt_set'
ld: drivers/rtc/rtc-bd70528.o: in function `bd70528_set_time':
drivers/rtc/rtc-bd70528.c:329: undefined reference to `bd70528_wdt_lock'
ld: drivers/rtc/rtc-bd70528.c:331: undefined reference to `bd70528_wdt_unlock'
vim +365 drivers/rtc/rtc-bd70528.c
355
356 static int bd70528_alm_enable(struct device *dev, unsigned int enabled)
357 {
358 int ret;
359 unsigned int enableval = BD70528_MASK_ALM_EN;
360 struct bd70528_rtc *r = dev_get_drvdata(dev);
361
362 if (enabled)
363 enableval = 0;
364
> 365 bd70528_wdt_lock(r->mfd);
366 ret = bd70528_set_wake(r->mfd, enabled, NULL);
367 if (ret) {
368 dev_err(dev, "Failed to change wake state\n");
369 goto out_unlock;
370 }
371 ret = regmap_update_bits(r->mfd->regmap, BD70528_REG_RTC_ALM_MASK,
372 BD70528_MASK_ALM_EN, enableval);
373 if (ret)
374 dev_err(dev, "Failed to change alarm state\n");
375
376 out_unlock:
> 377 bd70528_wdt_unlock(r->mfd);
378 return ret;
379 }
380
---
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: 30778 bytes --]
reply other threads:[~2019-08-07 16:57 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=201908080032.EH17lRAx%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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
all inboxes | Powered by JetHome®