All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: dyoung@redhat.com, dzickus@redhat.com,
	linux-watchdog@vger.kernel.org,
	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 V3 2/2] watchdog: Read device status through sysfs attributes
Date: Thu, 3 Sep 2015 16:54:16 +0530	[thread overview]
Message-ID: <20150903112416.GA636@dhcppc13.redhat.com> (raw)
In-Reply-To: <55E82670.2090101@roeck-us.net>

On 03/09/2015:03:52:32 AM, Guenter Roeck wrote:
> On 09/02/2015 08:22 PM, Pratyush Anand wrote:
> >This patch adds following attributes to watchdog device's sysfs interface
> >to read its different status.
> >
> >* state - reads whether device is active or not
> >* identity - reads Watchdog device's identity string.
> >* timeout - reads current timeout.
> >* timeleft - reads timeleft before watchdog generates a reset
> >* bootstatus - reads status of the watchdog device at boot
> >* status - reads watchdog device's  internal status bits
> >* nowayout - reads whether nowayout feature was set or not
> >
> >Testing with iTCO_wdt:
> >  # cd /sys/class/watchdog/watchdog1/
> >  # ls
> >bootstatus  dev  device  identity  nowayout  power  state
> >subsystem  timeleft  timeout  uevent
> >  # cat identity
> >iTCO_wdt
> >  # cat timeout
> >30
> >  # cat state
> >inactive
> >  # echo > /dev/watchdog1
> >  # cat timeleft
> >26
> >  # cat state
> >active
> >  # cat bootstatus
> >0
> >  # cat nowayout
> >0
> >
> >Signed-off-by: Pratyush Anand <panand@redhat.com>
> 
> Looks good, except for
> 
> WARNING: please, no space before tabs
> #250: FILE: drivers/watchdog/watchdog_dev.c:693:
> +^I.dev_groups = ^Iwdt_groups,$
> 
> [ there is a space after '=' ]
> 
> Assuming you fix that,
> 
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> 

Thanks a lot for the review.
I will fix it and will send it again.

~Pratyush

      parent reply	other threads:[~2015-09-03 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  3:19 [PATCH V3 0/2] watchdog: Sysfs status read support Pratyush Anand
2015-09-03  3:21 ` [PATCH V3 1/2] watchdog: Use static struct class watchdog_class in stead of pointer Pratyush Anand
2015-09-03 10:42   ` Guenter Roeck
     [not found] ` <cover.1441249584.git.panand-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-03  3:22   ` [PATCH V3 2/2] watchdog: Read device status through sysfs attributes Pratyush Anand
2015-09-03  3:22     ` Pratyush Anand
     [not found]     ` <55E82670.2090101@roeck-us.net>
2015-09-03 11:24       ` 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=20150903112416.GA636@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.