From: Ravi Chandra Sadineni <ravisadineni@chromium.org>
To: rjw@rjwysocki.net, chenhong3@huawei.com,
ravisadineni@chromium.org, pavel@ucw.cz, ravisadineni@google.com,
dtor@google.com, len.brown@intel.com, gregkh@linuxfoundation.org
Cc: tbroch@google.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, rajatja@google.com, bleung@google.com
Subject: [PATCH] power: Print wakeup_count instead of event_count in the sysfs attribute.
Date: Fri, 1 Jun 2018 19:32:15 -0700 [thread overview]
Message-ID: <20180602023215.176521-1-ravisadineni@chromium.org> (raw)
Currently we show event_count instead of wakeup_count as part of per
device wakeup_count sysfs attribute. Change it to wakeup_count to make
it more meaningful.
Signed-off-by: Ravi Chandra Sadineni <ravisadineni@chromium.org>
---
drivers/base/power/sysfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/power/sysfs.c b/drivers/base/power/sysfs.c
index 0f651efc58a1a..d713738ce7967 100644
--- a/drivers/base/power/sysfs.c
+++ b/drivers/base/power/sysfs.c
@@ -353,7 +353,7 @@ static ssize_t wakeup_count_show(struct device *dev,
spin_lock_irq(&dev->power.lock);
if (dev->power.wakeup) {
- count = dev->power.wakeup->event_count;
+ count = dev->power.wakeup->wakeup_count;
enabled = true;
}
spin_unlock_irq(&dev->power.lock);
--
2.17.1.1185.g55be947832-goog
next reply other threads:[~2018-06-02 2:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 2:32 Ravi Chandra Sadineni [this message]
2018-06-02 19:02 ` [PATCH] power: Print wakeup_count instead of event_count in the sysfs attribute Pavel Machek
2018-06-03 8:05 ` Rafael J. Wysocki
2018-06-03 17:14 ` Ravi Chandra Sadineni
2018-06-07 16:47 ` Ravi Chandra Sadineni
2018-06-08 9:16 ` Rafael J. Wysocki
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=20180602023215.176521-1-ravisadineni@chromium.org \
--to=ravisadineni@chromium.org \
--cc=bleung@google.com \
--cc=chenhong3@huawei.com \
--cc=dtor@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rajatja@google.com \
--cc=ravisadineni@google.com \
--cc=rjw@rjwysocki.net \
--cc=tbroch@google.com \
/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).