From: Paul Cercueil <paul@crapouillou.net>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>,
list@opendingux.net, linux-iio@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BROADCOM NVRAM DRIVER <linux-mips@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v3 0/6] DEV_PM_OPS macros rework v3
Date: Mon, 17 Jan 2022 16:57:52 +0000 [thread overview]
Message-ID: <GS5V5R.BVK5SB217XZU2@crapouillou.net> (raw)
In-Reply-To: <CAJZ5v0htDq+qFhEoV+PLQ9_pOy_xa7+rMoaGtqK7QpEbpUDA+Q@mail.gmail.com>
Le lun., janv. 17 2022 at 14:37:45 +0100, Rafael J. Wysocki
<rafael@kernel.org> a écrit :
> Hi,
>
> On Sun, Jan 16, 2022 at 1:05 PM Paul Cercueil <paul@crapouillou.net>
> wrote:
>>
>> Hi Rafael,
>>
>> Could patches [1/6] and [2/6] make it to 5.17-rc1, or at least -rc2?
>
> Yes. I'm going to send a PR with the whole series later today.
Ok, perfect then. I saw my previous PM patches in upstream/master and
assumed that you already sent your PR.
Cheers,
-Paul
>
>> I'm afraid that if these two have to wait for the 5.18 cycle, then
>> I'll
>> have more drivers to fix later.
>>
>> Should I add a Fixes tag maybe?
>
> No need, thanks!
>
>> Le ven., janv. 7 2022 at 18:17:17 +0000, Paul Cercueil
>> <paul@crapouillou.net> a écrit :
>> > Hi,
>> >
>> > A V2 of my patchset that tweaks a bit the *_DEV_PM_OPS() macros
>> that
>> > were introduced recently.
>> >
>> > Changes since V2:
>> > * [1/6]: - Keep UNIVERSAL_DEV_PM_OPS() macro deprecated
>> > - Rework commit message
>> > * [3/6]: - Reorder the code to have non-private macros together
>> in the
>> > file
>> > - Add comment about the necesity to use the new export
>> macro
>> > when the dev_pm_ops has to be exported
>> > * [5/6]: Add comment about the necesity to use the new export
>> macro
>> > when the dev_pm_ops has to be exported
>> >
>> > Cheers,
>> > -Paul
>> >
>> > Paul Cercueil (6):
>> > PM: core: Remove DEFINE_UNIVERSAL_DEV_PM_OPS() macro
>> > PM: core: Remove static qualifier in DEFINE_SIMPLE_DEV_PM_OPS
>> macro
>> > PM: core: Add EXPORT[_GPL]_SIMPLE_DEV_PM_OPS macros
>> > PM: runtime: Add DEFINE_RUNTIME_DEV_PM_OPS() macro
>> > PM: runtime: Add EXPORT[_GPL]_RUNTIME_DEV_PM_OPS macros
>> > iio: pressure: bmp280: Use new PM macros
>> >
>> > drivers/iio/pressure/bmp280-core.c | 11 ++----
>> > drivers/iio/pressure/bmp280-i2c.c | 2 +-
>> > drivers/iio/pressure/bmp280-spi.c | 2 +-
>> > drivers/mmc/host/jz4740_mmc.c | 4 +--
>> > drivers/mmc/host/mxcmmc.c | 2 +-
>> > include/linux/pm.h | 55
>> > ++++++++++++++++++++++--------
>> > include/linux/pm_runtime.h | 24 +++++++++++++
>> > 7 files changed, 71 insertions(+), 29 deletions(-)
>> >
>> > --
>> > 2.34.1
>> >
>>
>>
prev parent reply other threads:[~2022-01-17 16:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 18:17 [PATCH v3 0/6] DEV_PM_OPS macros rework v3 Paul Cercueil
2022-01-07 18:17 ` [PATCH v3 1/6] PM: core: Remove DEFINE_UNIVERSAL_DEV_PM_OPS() macro Paul Cercueil
2022-01-10 11:58 ` Ulf Hansson
2022-01-07 18:17 ` [PATCH v3 2/6] PM: core: Remove static qualifier in DEFINE_SIMPLE_DEV_PM_OPS macro Paul Cercueil
2022-01-07 18:17 ` [PATCH v3 3/6] PM: core: Add EXPORT[_GPL]_SIMPLE_DEV_PM_OPS macros Paul Cercueil
2022-01-08 17:38 ` Jonathan Cameron
2022-01-10 12:18 ` Ulf Hansson
2022-01-07 18:17 ` [PATCH v3 4/6] PM: runtime: Add DEFINE_RUNTIME_DEV_PM_OPS() macro Paul Cercueil
2022-01-10 12:18 ` Ulf Hansson
2022-01-07 18:17 ` [PATCH v3 5/6] PM: runtime: Add EXPORT[_GPL]_RUNTIME_DEV_PM_OPS macros Paul Cercueil
2022-01-10 12:19 ` Ulf Hansson
2022-01-07 18:17 ` [PATCH v3 6/6] iio: pressure: bmp280: Use new PM macros Paul Cercueil
2022-01-10 12:19 ` Ulf Hansson
2022-01-07 18:20 ` [PATCH v3 0/6] DEV_PM_OPS macros rework v3 Paul Cercueil
2022-01-16 12:05 ` Paul Cercueil
2022-01-17 13:37 ` Rafael J. Wysocki
2022-01-17 16:57 ` Paul Cercueil [this message]
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=GS5V5R.BVK5SB217XZU2@crapouillou.net \
--to=paul@crapouillou.net \
--cc=arnd@arndb.de \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=len.brown@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--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=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