From: Dhruva Gole <d-gole@ti.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Viresh Kumar <viresh.kumar@linaro.org>, <theo.lebrun@bootlin.com>,
Dhruva Gole <d-gole@ti.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>
Subject: [PATCH V2 0/2] PM: wakeup: make device_wakeup_disable return void
Date: Mon, 18 Mar 2024 20:46:30 +0530 [thread overview]
Message-ID: <20240318151631.1621881-1-d-gole@ti.com> (raw)
This is a follow up patch based on discussions with Rafael[0] on a previous
patch I sent to propagate return value from device_wakeup_disable
further upward inside device_init_wakeup
However, it doesn't seem like today any return values from
device_wakeup_disable are very useful to the caller.
I could only spot one caller of this function that was actually
propagating the return value upward other than the PM core calls. I have
tried to update sdhci-pci-core to work with the new changes
[0] https://lore.kernel.org/all/CAJZ5v0jbHwiZemtNAoM-jmgB_58VqmKUkqv4P7qrPkxWzBzMyQ@mail.gmail.com/
Changelog:
v1 --> v2:
* Squashed the mmc fix into first patch [Rafael]
Dhruva Gole (2):
PM: wakeup: make device_wakeup_disable return void
PM: wakeup: Remove unnecessary else from device_init_wakeup
drivers/base/power/wakeup.c | 11 +++++++----
drivers/mmc/host/sdhci-pci-core.c | 2 +-
include/linux/pm_wakeup.h | 12 +++++-------
3 files changed, 13 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2024-03-18 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:16 Dhruva Gole [this message]
2024-03-18 15:16 ` [PATCH V2 1/2] PM: wakeup: make device_wakeup_disable return void Dhruva Gole
2024-03-18 15:16 ` [PATCH V2 2/2] PM: wakeup: Remove unnecessary else from device_init_wakeup Dhruva Gole
2024-04-03 14:53 ` [PATCH V2 0/2] PM: wakeup: make device_wakeup_disable return void 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=20240318151631.1621881-1-d-gole@ti.com \
--to=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=theo.lebrun@bootlin.com \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).