public inbox for linux-watchdog@vger.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org, Dave Young <dyoung@redhat.com>,
	Don Zickus <dzickus@redhat.com>
Subject: Re: Query: Best way to know if a watchdog is active (kicked)
Date: Tue, 18 Aug 2015 18:38:07 +0530	[thread overview]
Message-ID: <20150818130807.GB12876@dhcppc13.redhat.com> (raw)
In-Reply-To: <55D329FE.2050005@roeck-us.net>

On 18/08/2015:05:50:06 AM, Guenter Roeck wrote:
> On 08/17/2015 11:57 PM, Pratyush Anand wrote:

[...]

> 
> One possible solution to your problem might be to have some sysfs attributes
> associated with watchdog devices, one of which would be its state.
> That has been on my mental task list for a while, but unfortunately
> I never found the time to implement it.

Well, I will give an attempt to implement state as a sysfs attributes associated
with watchdog devices, having two values ACTIVE and INACTIVE. Will send the
modification for review.
We can always add latter on more attributes and more state values.

Thanks a lot for your suggestion.

~Pratyush

  reply	other threads:[~2015-08-18 13:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  5:15 Query: Best way to know if a watchdog is active (kicked) Pratyush Anand
2015-08-18  5:39 ` Guenter Roeck
2015-08-18  6:57   ` Pratyush Anand
2015-08-18  9:13     ` Dave Young
2015-08-18  9:52       ` Pratyush Anand
2015-08-18 12:50     ` Guenter Roeck
2015-08-18 13:08       ` Pratyush Anand [this message]
2015-08-18 14:23         ` Guenter Roeck
2015-08-21  8:52           ` Pratyush Anand
2015-08-21 15:19             ` Guenter Roeck
2015-08-21 17:05               ` Pratyush Anand
2015-08-21 17:13                 ` Guenter Roeck
2015-08-21 17:19                   ` Pratyush Anand

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=20150818130807.GB12876@dhcppc13.redhat.com \
    --to=panand@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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