From: Guenter Roeck <linux@roeck-us.net>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] watchdog: simplify definitions of WATCHDOG_NOWAYOUT(_INIT_STATUS)?
Date: Thu, 11 Sep 2014 08:42:04 -0700 [thread overview]
Message-ID: <20140911154204.GA27637@roeck-us.net> (raw)
In-Reply-To: <1410293911-18392-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Tue, Sep 09, 2014 at 10:18:31PM +0200, Uwe Kleine-König wrote:
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
>
> maybe it's arguable if the newly introduced way to define
> WATCHDOG_NOWAYOUT and WATCHDOG_NOWAYOUT_INIT_STATUS is really simpler.
> But at least it's five lines shorter and makes the questionable naming
> of cpp symbols more obvious. (Who can tell the difference between
> the semantic of WATCHDOG_NOWAYOUT and WDOG_NO_WAY_OUT without further
> checking?)
>
I like it.
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Guenter
> Best regards
> Uwe
>
> include/linux/watchdog.h | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/include/linux/watchdog.h b/include/linux/watchdog.h
> index 2a3038ee17a3..395b70e0eccf 100644
> --- a/include/linux/watchdog.h
> +++ b/include/linux/watchdog.h
> @@ -97,13 +97,8 @@ struct watchdog_device {
> #define WDOG_UNREGISTERED 4 /* Has the device been unregistered */
> };
>
> -#ifdef CONFIG_WATCHDOG_NOWAYOUT
> -#define WATCHDOG_NOWAYOUT 1
> -#define WATCHDOG_NOWAYOUT_INIT_STATUS (1 << WDOG_NO_WAY_OUT)
> -#else
> -#define WATCHDOG_NOWAYOUT 0
> -#define WATCHDOG_NOWAYOUT_INIT_STATUS 0
> -#endif
> +#define WATCHDOG_NOWAYOUT IS_BUILTIN(CONFIG_WATCHDOG_NOWAYOUT)
> +#define WATCHDOG_NOWAYOUT_INIT_STATUS (WATCHDOG_NOWAYOUT << WDOG_NO_WAY_OUT)
>
> /* Use the following function to check whether or not the watchdog is active */
> static inline bool watchdog_active(struct watchdog_device *wdd)
> --
> 2.1.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-11 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 20:18 [PATCH] watchdog: simplify definitions of WATCHDOG_NOWAYOUT(_INIT_STATUS)? Uwe Kleine-König
2014-09-11 15:42 ` Guenter Roeck [this message]
2014-09-16 15:49 ` Uwe Kleine-König
2014-09-18 15:32 ` Guenter Roeck
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=20140911154204.GA27637@roeck-us.net \
--to=linux@roeck-us.net \
--cc=kernel@pengutronix.de \
--cc=linux-watchdog@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--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