linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [PATCH RFC] watchdog: Add watchdog device control through sysfs attributes
Date: Wed, 26 Aug 2015 04:49:17 +0530	[thread overview]
Message-ID: <20150825231917.GD13340@dhcppc13.redhat.com> (raw)
In-Reply-To: <55DCA3C1.5050307@roeck-us.net>

On 25/08/2015:10:20:01 AM, Guenter Roeck wrote:
> On 08/25/2015 09:45 AM, Pratyush Anand wrote:
> >Hi Guenter,
> >
> >On 21/08/2015:11:18:12 PM, Pratyush Anand wrote:
> >>This patch adds following attributes to watchdog device's sysfs interface.
> >
> >Please see if you can review it.
> >
> >Does this patch look fine to you? If yes then do I need to resend it by removing
> >RFC tag.
> >
> 
> I didn't have time to review your patch in detail. Sorry, but please keep in mind
> that this is all volunteer work for me.

It's understandable. Sorry for my impatience. Please take your time.

> 
> I don't feel comfortable with modifying the watchdog state through sysfs.
> That changes the ABI substantially, since it is no longer necessary to have
> an application to activate the watchdog. It also messes up internal state keeping,
> since there is now no longer a well defined state indicating that the kernel
> expects user space to send heartbeats, or if the kernel needs to do it (in the
> driver or, with the patch set I submitted a couple of weeks ago, in the watchdog
> core).

I will be OK with removing 'start'.

> 
> Given that, and I really don't have time to look into it more deeply,
> I put the whole thing on a back burner for now.
> 

No issue, will wait :-)

~Pratyush

  parent reply	other threads:[~2015-08-25 23:19 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 [this message]
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

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=20150825231917.GD13340@dhcppc13.redhat.com \
    --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).