From: Wim Van Sebroeck <wim@iguana.be>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
poeschel@lemonage.de, Jonathan Corbet <corbet@lwn.net>,
LKML doc <linux-doc@vger.kernel.org>,
linux-watchdog@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH v2] watchdog: omap_wdt: early_enable module parameter
Date: Tue, 30 Jun 2015 08:58:07 +0200 [thread overview]
Message-ID: <20150630065807.GA5645@spo001.leaseweb.nl> (raw)
In-Reply-To: <CAP=VYLr5wVMBdA76U0HKP2GTN07qiCkCTtBmFG5Z_bWE0QvT9g@mail.gmail.com>
Hi Paul,
> On Thu, Jun 25, 2015 at 9:46 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> > On 06/25/2015 03:21 AM, poeschel@lemonage.de wrote:
> >>
> >> From: Lars Poeschel <poeschel@lemonage.de>
> >>
> >> Add a early_enable module parameter to the omap_wdt that starts the
> >> watchdog on module insertion. The default value is 0 which does not
> >> start the watchdog - which also does not change the behavior if the
> >> parameter is not given.
> >>
> >> Signed-off-by: Lars Poeschel <poeschel@lemonage.de>
> >
> >
> > Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>
> In case the info hasn't looped back around yet, this breaks the
> omap builds in linux-next:
>
> drivers/watchdog/omap_wdt.c:288:18: error: 'omap_wdt' undeclared
> (first use in this function)
>
> (Not sure how this could have ever worked as-is.)
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12452335/
>
> I see a patch has already been posted to arm-kernel but not
> Cc'd to all originally involved so figured I'd mention it.
It's fixed. The reason why we din't catch it was because of interference
with 'watchdog: omap: put struct watchdog_device into driver data'.
Kind regards,
Wim.
prev parent reply other threads:[~2015-06-30 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 10:21 poeschel
2015-06-25 13:46 ` Guenter Roeck
2015-06-30 5:56 ` Paul Gortmaker
2015-06-30 6:58 ` Wim Van Sebroeck [this message]
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=20150630065807.GA5645@spo001.leaseweb.nl \
--to=wim@iguana.be \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=paul.gortmaker@windriver.com \
--cc=poeschel@lemonage.de \
/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
all inboxes | Powered by JetHome®