All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build failure after merge of the watchdog tree
Date: Mon, 21 Jun 2021 10:08:20 +0200	[thread overview]
Message-ID: <20210621080820.GA20712@infomag.iguana.be> (raw)
In-Reply-To: <20210621153839.43dd423e@canb.auug.org.au>

Hi Stephen,

Fixed for tomorrow's pull.

Kind regards,
Wim.

> 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



  reply	other threads:[~2021-06-21  8:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21  5:38 linux-next: build failure after merge of the watchdog tree Stephen Rothwell
2021-06-21  8:08 ` Wim Van Sebroeck [this message]
2021-06-22 15:27 ` Vaittinen, Matti
  -- strict thread matches above, loose matches on Subject: below --
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=20210621080820.GA20712@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.