From: Paul Cercueil <paul@crapouillou.net>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Jonathan Cameron <jic23@kernel.org>
Cc: list@opendingux.net, linux-mips@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-pm@vger.kernel.org,
Paul Cercueil <paul@crapouillou.net>
Subject: [PATCH 0/5] Rework pm_ptr() and *_PM_OPS macros
Date: Tue, 7 Dec 2021 00:20:57 +0000 [thread overview]
Message-ID: <20211207002102.26414-1-paul@crapouillou.net> (raw)
Hi,
This patchset reworks the pm_ptr() macro I introduced a few versions
ago, so that it is not conditionally defined.
It applies the same treatment to the *_PM_OPS macros. Instead of
modifying the existing ones, which would mean a 2000+ patch bomb, this
patchset introduce two new macros to replace the now deprecated
UNIVERSAL_DEV_PM_OPS() and SIMPLE_DEV_PM_OPS().
The point of all of this, is to progressively switch from a code model
where PM callbacks are all protected behind CONFIG_PM guards, to a code
model where PM callbacks are always seen by the compiler, but discarded
if not used.
Patch [4/5] and [5/5] are just examples to illustrate the use of the new
macros. As such they don't really have to be merged at the same time as
the rest and can be delayed until a subsystem-wide patchset is proposed.
- Patch [4/5] modifies a driver that already used the pm_ptr() macro,
but had to use the __maybe_unused flag to avoid compiler warnings;
- Patch [5/5] modifies a driver that used a #ifdef CONFIG_PM guard
around its suspend/resume functions.
Paul Cercueil (5):
r8169: Avoid misuse of pm_ptr() macro
PM: core: Redefine pm_ptr() macro
PM: core: Add new *_PM_OPS macros, deprecate old ones
mmc: jz4740: Use the new PM macros
mmc: mxc: Use the new PM macros
drivers/mmc/host/jz4740_mmc.c | 8 +--
drivers/mmc/host/mxcmmc.c | 6 +-
drivers/net/ethernet/realtek/r8169_main.c | 4 +-
include/linux/pm.h | 80 +++++++++++++++--------
4 files changed, 60 insertions(+), 38 deletions(-)
--
2.33.0
next reply other threads:[~2021-12-07 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 0:20 Paul Cercueil [this message]
2021-12-07 0:20 ` [PATCH 1/5] r8169: Avoid misuse of pm_ptr() macro Paul Cercueil
2021-12-07 0:20 ` [PATCH 2/5] PM: core: Redefine " Paul Cercueil
2021-12-16 11:10 ` Jonathan Cameron
2021-12-07 0:21 ` [PATCH 3/5] PM: core: Add new *_PM_OPS macros, deprecate old ones Paul Cercueil
2021-12-16 11:09 ` Jonathan Cameron
2021-12-07 0:21 ` [PATCH 4/5] mmc: jz4740: Use the new PM macros Paul Cercueil
2021-12-07 0:21 ` [PATCH 5/5] mmc: mxc: " Paul Cercueil
2021-12-07 9:22 ` [PATCH 0/5] Rework pm_ptr() and *_PM_OPS macros Arnd Bergmann
2021-12-17 15:07 ` Rafael J. Wysocki
2021-12-17 17:16 ` Ulf Hansson
2021-12-17 18:22 ` 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=20211207002102.26414-1-paul@crapouillou.net \
--to=paul@crapouillou.net \
--cc=arnd@arndb.de \
--cc=jic23@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=list@opendingux.net \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=ulf.hansson@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 NNTP newsgroup(s).