From: Greg KH <gregkh@linuxfoundation.org>
To: Ravi Chandra Sadineni <ravisadineni@chromium.org>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, x86@kernel.org, rjw@rjwysocki.net, pavel@ucw.cz,
len.brown@intel.com, bhe@redhat.com, dyoung@redhat.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
tbroch@chromium.org
Subject: Re: [PATCH 1/2 V2] power: sysfs: Remove wakeup_abort_count attribute.
Date: Tue, 23 Jul 2019 09:07:23 +0200 [thread overview]
Message-ID: <20190723070723.GE27629@kroah.com> (raw)
In-Reply-To: <20190722223337.36199-2-ravisadineni@chromium.org>
On Mon, Jul 22, 2019 at 03:33:36PM -0700, Ravi Chandra Sadineni wrote:
> wakeup_abort_count and wakeup_count sysfs entries print the
> same (wakeup_count) attribute. This patch removes the duplicate
> wakeup_abort_count sysfs entry.
Are you sure that userspace is not using this "duplicate" entry? Have
you searched userspace tools to verify this?
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-23 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 17:04 [PATCH] power: sysfs: Remove wakeup_abort_count attribute Ravi Chandra Sadineni
2019-07-22 18:24 ` Greg KH
2019-07-22 22:33 ` [PATCH 0/2] power: Refactor device level sysfs Ravi Chandra Sadineni
2019-07-22 22:33 ` [PATCH 1/2 V2] power: sysfs: Remove wakeup_abort_count attribute Ravi Chandra Sadineni
2019-07-23 7:07 ` Greg KH [this message]
2019-07-22 22:33 ` [PATCH 2/2 V2] power:sysfs: Expose device wakeup_event_count Ravi Chandra Sadineni
2019-07-23 7:07 ` Greg KH
2019-07-23 7:44 ` [PATCH 0/2] power: Refactor device level sysfs Rafael J. Wysocki
2019-07-23 16:56 ` Ravi Chandra Sadineni
2019-07-23 17:02 ` Rafael J. Wysocki
2019-07-23 17:25 ` Ravi Chandra Sadineni
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=20190723070723.GE27629@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=ravisadineni@chromium.org \
--cc=rjw@rjwysocki.net \
--cc=tbroch@chromium.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).