From: Stephen Boyd <swboyd@chromium.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Qian Cai <cai@lca.pw>, Tri Vo <trong@android.com>
Subject: [PATCH v4 0/2] PM / wakeup: Fix wakeup class wrecakge in -next
Date: Mon, 19 Aug 2019 15:41:56 -0700 [thread overview]
Message-ID: <20190819224158.62954-1-swboyd@chromium.org> (raw)
Resending the patch series to pick up the tags and fix the subject
on patch #2. I didn't drop the "Fixes" tags even though they're
just in -next and the patches have been dropped in the latest version.
Please update them in the future so we know what commit they're fixing
if the commits change in the pm tree.
Changes from v3:
* Picked up reviewed-by tags from Tri Vo
* Fixed Cc tag on patch 2
* Fixed subject on patch 2 to speak about proper symbols
Changes from v2:
* Fix logic for not adding the wakeup class from dpm_sysfs_add()
* Compile tested on !CONFIG_PM_SLEEP
Cc: Qian Cai <cai@lca.pw>
Cc: Tri Vo <trong@android.com>
Stephen Boyd (2):
PM / wakeup: Register wakeup class kobj after device is added
PM / wakeup: Unexport wakeup_source_sysfs_{add,remove}()
drivers/base/power/power.h | 9 +++++++++
drivers/base/power/sysfs.c | 6 ++++++
drivers/base/power/wakeup.c | 10 ++++++----
drivers/base/power/wakeup_stats.c | 15 +++++++++++++--
4 files changed, 34 insertions(+), 6 deletions(-)
base-commit: 0c3d3d648b3ed72b920a89bc4fd125e9b7aa5f23
--
Sent by a computer through tubes
next reply other threads:[~2019-08-19 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 22:41 Stephen Boyd [this message]
2019-08-19 22:41 ` [PATCH v4 1/2] PM / wakeup: Register wakeup class kobj after device is added Stephen Boyd
2019-08-19 22:41 ` [PATCH v4 2/2] PM / wakeup: Unexport wakeup_source_sysfs_{add,remove}() Stephen Boyd
2019-08-26 9:21 ` [PATCH v4 0/2] PM / wakeup: Fix wakeup class wrecakge in -next 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=20190819224158.62954-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=trong@android.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