All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pramod Gurav <pramod.gurav@smartplayin.com>
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>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: linux-next: build failure after merge of the watchdog tree
Date: Fri, 26 Sep 2014 11:26:04 +0530	[thread overview]
Message-ID: <5424FFF4.4010506@smartplayin.com> (raw)
In-Reply-To: <20140926154031.4bc4dc39@canb.auug.org.au>

On Friday 26 September 2014 11:10 AM, 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);
>   ^
>
This is because Guenter Roeck's restart_notifier mechanism [1] has not
yet made it to linux-next.

Oh yes, I checked it now its already pulled in master branch of linux-next.

> Caused by commit 575f4153957b ("ARM: meson: add watchdog driver").
> 
> I have reverted that commit for today.
> 
[1]: https://patchwork.kernel.org/patch/4746721/

Thanks
Pramod

  parent reply	other threads:[~2014-09-26  5:52 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
2014-09-26  5:56 ` Pramod Gurav [this message]
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=5424FFF4.4010506@smartplayin.com \
    --to=pramod.gurav@smartplayin.com \
    --cc=carlo@caione.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 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.