From: Pratyush Anand <panand@redhat.com>
To: wim@iguana.be
Cc: dyoung@redhat.com, dzickus@redhat.com, linux@roeck-us.net,
linux-watchdog@vger.kernel.org,
Pratyush Anand <panand@redhat.com>
Subject: [PATCH V5 0/2] watchdog: Sysfs status read support
Date: Thu, 17 Dec 2015 17:53:57 +0530 [thread overview]
Message-ID: <cover.1450353452.git.panand@redhat.com> (raw)
These patches provide support to read different watchdog device status
through sysfs interface.
Changes since V4:
* All sysfs code has been protected under CONFIG_WATCHDOG_SYSFS
Changes since V3:
* Added Reviewed by tag
* Corrected a checkpatch warning
Changes since V2:
* Used static struct class watchdog_class in stead of pointer. It helped to
keep using device_create().
* Above logic was moved to a separate patch. Changed subject line of other
patch to look more relevant
Changes since V1(RFC):
* Removed keepalive and start ABI
* timeout is read only now
* state returns text
* only supported ABI visible
* ABI contact changed to MAINTAINER
* unnecessary mutex removed
* aligned continuation with '('
* unnecessary initialization of status (= 0) corrected
* unnecessary else removed
* used __ATTRIBUTE_GROUPS
* removed watchdog_device_create and added functionality in
* watchdog_dev_register.
* optimized nowayout_show
* Now no -EOPNOTSUPP return for timeout read in case of
* wdd->timeout = 0.
Pratyush Anand (2):
watchdog: Use static struct class watchdog_class in stead of pointer
watchdog: Read device status through sysfs attributes
Documentation/ABI/testing/sysfs-class-watchdog | 51 +++++++++
drivers/watchdog/Kconfig | 7 ++
drivers/watchdog/watchdog_core.c | 17 +--
drivers/watchdog/watchdog_core.h | 2 +-
drivers/watchdog/watchdog_dev.c | 140 ++++++++++++++++++++++++-
5 files changed, 198 insertions(+), 19 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-class-watchdog
--
2.5.0
next reply other threads:[~2015-12-17 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 12:23 Pratyush Anand [this message]
2015-12-17 12:23 ` [PATCH V5 1/2] watchdog: Use static struct class watchdog_class in stead of pointer Pratyush Anand
2015-12-17 14:56 ` Guenter Roeck
2015-12-19 4:22 ` Pratyush Anand
2015-12-19 16:21 ` Guenter Roeck
2015-12-21 15:52 ` Guenter Roeck
2015-12-21 16:13 ` Pratyush Anand
2015-12-17 12:23 ` [PATCH V5 2/2] watchdog: Read device status through sysfs attributes Pratyush Anand
2015-12-17 14:53 ` Guenter Roeck
2015-12-27 16:57 ` [PATCH V5 0/2] watchdog: Sysfs status read support Wim Van Sebroeck
2015-12-28 4:14 ` 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=cover.1450353452.git.panand@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 \
--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).