From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Wim Van Sebroeck <wim@iguana•be>
Cc: Guenter Roeck <linux@roeck-us•net>,
Matti Vaittinen <matti.vaittinen@fi•rohmeurope.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the watchdog tree
Date: Mon, 21 Jun 2021 15:38:39 +1000 [thread overview]
Message-ID: <20210621153839.43dd423e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
Hi all,
After merging the watchdog tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: modpost: "bd70528_wdt_unlock" [drivers/rtc/rtc-bd70528.ko] undefined!
ERROR: modpost: "bd70528_wdt_lock" [drivers/rtc/rtc-bd70528.ko] undefined!
ERROR: modpost: "bd70528_wdt_set" [drivers/rtc/rtc-bd70528.ko] undefined!
Caused by commit
f2a5178b0b9f ("watchdog: bd70528 drop bd70528 support")
I have used the watchdog tree from next-20210618 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-21 5:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 5:38 Stephen Rothwell [this message]
2021-06-21 8:08 ` linux-next: build failure after merge of the watchdog tree Wim Van Sebroeck
2021-06-22 15:27 ` Vaittinen, Matti
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 10:03 Stephen Rothwell
2025-03-11 12:12 ` Mark Pearson
2025-03-11 14:54 ` Wim Van Sebroeck
2024-09-11 4:55 Stephen Rothwell
2024-09-11 10:42 ` Prabhakar Mahadev Lad
2024-09-11 10:48 ` Stephen Rothwell
2024-09-13 5:44 ` Stephen Rothwell
2024-09-13 8:31 ` Wim Van Sebroeck
2024-09-13 8:54 ` Prabhakar Mahadev Lad
2020-12-14 5:23 Stephen Rothwell
2020-12-14 6:09 ` Guenter Roeck
2020-12-16 2:56 ` Stephen Rothwell
2020-12-16 4:11 ` Guenter Roeck
2020-12-16 15:27 ` Wim Van Sebroeck
2020-12-17 7:04 ` Wim Van Sebroeck
2014-09-26 5:40 Stephen Rothwell
2014-09-26 5:51 ` Guenter Roeck
2014-09-26 6:29 ` Stephen Rothwell
2014-09-26 6:49 ` Guenter Roeck
2014-09-26 5:56 ` Pramod Gurav
2014-09-26 6:12 ` Guenter Roeck
2014-09-26 6:34 ` Stephen Rothwell
2014-09-26 6:47 ` Guenter Roeck
2011-11-01 5:37 Stephen Rothwell
2011-11-01 12:02 ` Mark Brown
2011-11-02 16:43 ` Wim Van Sebroeck
2011-01-10 3:12 Stephen Rothwell
2011-01-10 7:27 ` Wim Van Sebroeck
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=20210621153839.43dd423e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=matti.vaittinen@fi$(echo .)rohmeurope.com \
--cc=wim@iguana$(echo .)be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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