From: Randy Dunlap <rdunlap@infradead.org>
To: Guenter Roeck <linux@roeck-us.net>,
kbuild test robot <lkp@intel.com>,
Marco Felsch <m.felsch@pengutronix.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Stefan Lengfeld <contact@stefanchrist.eu>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Subject: Re: da9062_wdt.c:undefined reference to `i2c_smbus_write_byte_data'
Date: Sat, 8 Feb 2020 09:21:07 -0800 [thread overview]
Message-ID: <9ff9f4ae-84e8-e660-fa53-c94cd303e42c@infradead.org> (raw)
In-Reply-To: <184bc727-2cb5-a3c2-38ee-83da8dbd0396@roeck-us.net>
On 2/8/20 8:38 AM, Guenter Roeck wrote:
> On 2/8/20 8:06 AM, Randy Dunlap wrote:
>> On 2/8/20 5:14 AM, kbuild test robot wrote:
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>> head: f757165705e92db62f85a1ad287e9251d1f2cd82
>>> commit: 057b52b4b3d58f4ee5944171da50f77b00a1bb0d watchdog: da9062: make restart handler atomic safe
>>> date: 12 days ago
>>> config: i386-randconfig-b001-20200208 (attached as .config)
>>> compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
>>> reproduce:
>>> git checkout 057b52b4b3d58f4ee5944171da50f77b00a1bb0d
>>> # save the attached .config to linux build tree
>>> make ARCH=i386
>>>
>>> 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/watchdog/da9062_wdt.o: in function `da9062_wdt_restart':
>>>>> da9062_wdt.c:(.text+0x1c): undefined reference to `i2c_smbus_write_byte_data'
>>>
>>> ---
>>> 0-DAY CI Kernel Test Service, Intel Corporation
>>> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>>
>>
>> Also reported here:
>> https://lore.kernel.org/lkml/ac797eb0-9b0a-d2d3-3a40-3fbd0a8b5ee0@infradead.org/
>>
>
> Yes, I know, and 0-day reported it earlier as well. Unfortunately
> neither resulted in a fix. I submitted one last night; see
> https://patchwork.kernel.org/patch/11371651/.
Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
Thanks.
--
~Randy
next prev parent reply other threads:[~2020-02-08 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 13:14 kbuild test robot
2020-02-08 16:06 ` Randy Dunlap
2020-02-08 16:38 ` Guenter Roeck
2020-02-08 17:21 ` Randy Dunlap [this message]
2020-02-10 8:47 ` Marco Felsch
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=9ff9f4ae-84e8-e660-fa53-c94cd303e42c@infradead.org \
--to=rdunlap@infradead.org \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=contact@stefanchrist.eu \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=m.felsch@pengutronix.de \
--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
all inboxes | Powered by JetHome®