linux-kernel - Re: linux-next: build failure after merge of the watchdog tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Sep 2014 22:51:28 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Wim Van Sebroeck <wim@...ana.be>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Carlo Caione <carlo@...one.org>
Subject: Re: linux-next: build failure after merge of the watchdog tree

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 ?

Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/