From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Ulf Hansson <ulf.hansson@linaro.org>,
od@zcrc.me, linux-mmc <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] PM: introduce pm_ptr() macro
Date: Mon, 27 Jul 2020 13:54:35 +0200 [thread overview]
Message-ID: <CAJZ5v0ju0KhXdfniZYqmZs+EmMx4U01RJZu3DVYazPYk6pK=Cg@mail.gmail.com> (raw)
In-Reply-To: <20200716124250.9829-1-paul@crapouillou.net>
On Thu, Jul 16, 2020 at 2:43 PM Paul Cercueil <paul@crapouillou.net> wrote:
>
> This macro is analogous to the infamous of_match_ptr(). If CONFIG_PM
> is enabled, this macro will resolve to its argument, otherwise to NULL.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
> ---
>
> Notes:
> v2: Remove pm_sleep_ptr() macro
> v3: Rebase on 5.8-rc5 and add Ulf's Reviewed-by
>
> include/linux/pm.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/pm.h b/include/linux/pm.h
> index 121c104a4090..1f227c518db3 100644
> --- a/include/linux/pm.h
> +++ b/include/linux/pm.h
> @@ -374,6 +374,12 @@ const struct dev_pm_ops name = { \
> SET_RUNTIME_PM_OPS(suspend_fn, resume_fn, idle_fn) \
> }
>
> +#ifdef CONFIG_PM
> +#define pm_ptr(_ptr) (_ptr)
> +#else
> +#define pm_ptr(_ptr) NULL
> +#endif
> +
> /*
> * PM_EVENT_ messages
> *
> --
Applied along with the [2-3/3] as 5.9 material, thanks!
prev parent reply other threads:[~2020-07-27 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 12:42 [PATCH v3 1/3] PM: introduce pm_ptr() macro Paul Cercueil
2020-07-16 12:42 ` [PATCH v3 2/3] PM: Make *_DEV_PM_OPS macros use __maybe_unused Paul Cercueil
2020-07-16 12:42 ` [PATCH v3 3/3] mmc: jz4740: Use pm_ptr() macro Paul Cercueil
2020-07-27 11:54 ` Rafael J. Wysocki [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='CAJZ5v0ju0KhXdfniZYqmZs+EmMx4U01RJZu3DVYazPYk6pK=Cg@mail.gmail.com' \
--to=rafael@kernel.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=od@zcrc.me \
--cc=paul@crapouillou.net \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--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).