From: Pratyush Anand <panand@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org, dyoung@redhat.com,
dzickus@redhat.com,
open list: ABI/API <linux-api@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [RFC] watchdog: Add watchdog device control through sysfs attributes
Date: Mon, 31 Aug 2015 10:56:06 +0530 [thread overview]
Message-ID: <20150831052606.GD4660@dhcppc13> (raw)
In-Reply-To: <55E3CDBC.2040109@roeck-us.net>
On 30/08/2015:08:45:00 PM, Guenter Roeck wrote:
> On 08/30/2015 08:11 PM, Pratyush Anand wrote:
> >On 29/08/2015:09:51:24 AM, Guenter Roeck wrote:
> >>>* timeout - reads current timeout and writes to program a new timeout.
> >
> >Now, this is the only file which has write permission. I hope, that is fine. Pl
> >let me know if you expected this to be as RO as well.
> >
> Good question. Thinking about it, we should make it read-only. Reason is
> that the application sending the heartbeats would not know about timeout
> changes made through sysfs, which could (and likely would) be fatal.
OK..will change accordingly.
~Pratyush
prev parent reply other threads:[~2015-08-31 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 17:48 [PATCH RFC] watchdog: Add watchdog device control through sysfs attributes Pratyush Anand
2015-08-25 16:45 ` Pratyush Anand
[not found] ` <55DCA3C1.5050307@roeck-us.net>
2015-08-25 23:19 ` Pratyush Anand
2015-08-29 16:51 ` [RFC] " Guenter Roeck
2015-08-30 14:16 ` Pratyush Anand
[not found] ` <55E31A13.80503@roeck-us.net>
2015-08-30 18:17 ` Pratyush Anand
[not found] ` <55E34DEA.7010206@roeck-us.net>
2015-08-31 3:04 ` Pratyush Anand
2015-08-31 3:11 ` Pratyush Anand
[not found] ` <55E3CDBC.2040109@roeck-us.net>
2015-08-31 5:26 ` Pratyush Anand [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=20150831052606.GD4660@dhcppc13 \
--to=panand@redhat.com \
--cc=dyoung@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).