linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-watchdog@vger.kernel.org, wim@iguana.be
Subject: Re: [PATCH 2/4] watchdog: Add a flag to indicate the watchdog doesn't reboot things
Date: Fri, 13 Apr 2012 10:58:12 +0200	[thread overview]
Message-ID: <4F87EAA4.3090900@redhat.com> (raw)
In-Reply-To: <20120321152503.20045.41514.stgit@bob.linux.org.uk>

Looks good, ack.

Acked-by: Hans de Goede <hdegoede@redhat.com>

On 03/21/2012 04:25 PM, Alan Cox wrote:
> From: Alan Cox<alan@linux.intel.com>
>
> Some watchdogs merely trigger external alarms and controls. In a managed
> environment this is very useful but we want drivers to be able to figure
> out which is which now multiple dogs can be loaded. Thus add an ALARMONLY
> feature flag.
>
> Signed-off-by: Alan Cox<alan@linux.intel.com>
> ---
>
>   include/linux/watchdog.h |    2 ++
>   1 files changed, 2 insertions(+), 0 deletions(-)
>
>
> diff --git a/include/linux/watchdog.h b/include/linux/watchdog.h
> index 0d5c3af..fdd5dbb 100644
> --- a/include/linux/watchdog.h
> +++ b/include/linux/watchdog.h
> @@ -45,6 +45,8 @@ struct watchdog_info {
>   #define	WDIOF_SETTIMEOUT	0x0080  /* Set timeout (in seconds) */
>   #define	WDIOF_MAGICCLOSE	0x0100	/* Supports magic close char */
>   #define	WDIOF_PRETIMEOUT	0x0200  /* Pretimeout (in seconds), get/set */
> +#define WDIOF_ALARMONLY		0x0400	/* Watchdog triggers a management or
> +					   other external alarm not a reboot */
>   #define	WDIOF_KEEPALIVEPING	0x8000	/* Keep alive ping reply */
>
>   #define	WDIOS_DISABLECARD	0x0001	/* Turn off the watchdog timer */
>

  reply	other threads:[~2012-04-13  8:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 15:24 [PATCH 1/4] watchdog: Add multiple device support Alan Cox
2012-03-21 15:25 ` [PATCH 2/4] watchdog: Add a flag to indicate the watchdog doesn't reboot things Alan Cox
2012-04-13  8:58   ` Hans de Goede [this message]
2012-04-24 19:35     ` Wim Van Sebroeck
2012-03-21 15:25 ` [PATCH 3/4] watchdog: create all the proper device files Alan Cox
2012-04-13  8:59   ` Hans de Goede
2012-03-21 15:25 ` [PATCH 4/4] watchdog: use dev_ functions Alan Cox
2012-04-13  9:00   ` Hans de Goede
2012-04-13  8:57 ` [PATCH 1/4] watchdog: Add multiple device support Hans de Goede
2012-05-04 12:38 ` Wim Van Sebroeck
2012-05-10 19:20   ` Wim Van Sebroeck
2012-05-11  7:50     ` Hans de Goede
2012-05-11  8:42       ` Hans de Goede
2012-05-11 16:02       ` Wim Van Sebroeck
2012-05-11 16:40         ` Hans de Goede
2012-05-13 12:15           ` Tomas Winkler
2012-05-14 13:35             ` Wim Van Sebroeck
2012-05-11  9:58     ` Hans de Goede

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=4F87EAA4.3090900@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-watchdog@vger.kernel.org \
    --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).