From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Carlo Caione <carlo@caione.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: build failure after merge of the watchdog tree
Date: Thu, 25 Sep 2014 23:49:31 -0700 [thread overview]
Message-ID: <54250C7B.6070101@roeck-us.net> (raw)
In-Reply-To: <20140926162942.161863df@canb.auug.org.au>
On 09/25/2014 11:29 PM, Stephen Rothwell wrote:
> Hi Guenter,
>
> On Thu, 25 Sep 2014 22:51:28 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> On 09/25/2014 10:40 PM, Stephen Rothwell wrote:
>>> Hi Wim,
>>>
>>> After merging the watchdog tree, today's linux-next build (arm
>>> multi_v7_defconfig) failed like this:
>>>
>>>
>>> drivers/watchdog/meson_wdt.c: In function 'meson_wdt_probe':
>>> drivers/watchdog/meson_wdt.c:178:2: error: implicit declaration of function 'register_restart_handler' [-Werror=implicit-function-declaration]
>>> err = register_restart_handler(&meson_wdt->restart_handler);
>>> ^
>>> drivers/watchdog/meson_wdt.c: In function 'meson_wdt_remove':
>>> drivers/watchdog/meson_wdt.c:193:2: error: implicit declaration of function 'unregister_restart_handler' [-Werror=implicit-function-declaration]
>>> unregister_restart_handler(&meson_wdt->restart_handler);
>>> ^
>>>
>>> Caused by commit 575f4153957b ("ARM: meson: add watchdog driver").
>>>
>>> I have reverted that commit for today.
>>>
>>
>> Those functions are defined by patches which reside in Andrew's tree.
>> Is that merged later ?
>
> Yes, Andrew's tree is merged last and part of it depends on linux-next
> itself ...
>
> We really don't want these inter tree dependencies (especially with
> Andrew's tree).
>
Me not either. Question was how to get the restart handler patch set upstream.
Pushing it indirectly through merges of an immutable branch sounds like a good
idea, especially since there are by now patches in at least three subsystems
pending which depend on it.
Guenter
next prev parent reply other threads:[~2014-09-26 6:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 5:40 linux-next: build failure after merge of the watchdog tree Stephen Rothwell
2014-09-26 5:51 ` Guenter Roeck
2014-09-26 6:29 ` Stephen Rothwell
2014-09-26 6:49 ` Guenter Roeck [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2021-06-21 5:38 Stephen Rothwell
2021-06-21 8:08 ` Wim Van Sebroeck
2021-06-22 15:27 ` Vaittinen, Matti
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
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=54250C7B.6070101@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=carlo@caione.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wim@iguana.be \
/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).