[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2708095.iQXV2FnTNx@kreacher>
Date: Sun, 26 Apr 2020 17:40:43 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Paul Cercueil <paul@...pouillou.net>
Cc: Ulf Hansson <ulf.hansson@...aro.org>, Pavel Machek <pavel@....cz>,
Len Brown <len.brown@...el.com>, od@...c.me,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v2 1/3] PM: introduce pm_ptr() macro
On Monday, April 13, 2020 2:32:05 PM CEST Paul Cercueil 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.
Well, this is going to result in quite a bit of unused code being
added to the kernels built with CONFIG_PM unset.
Is there any way to avoid that somehow?
> Signed-off-by: Paul Cercueil <paul@...pouillou.net>
> ---
>
> Notes:
> v2: Remove pm_sleep_ptr() macro
>
> include/linux/pm.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/pm.h b/include/linux/pm.h
> index e057d1fa2469..1c0eec06905d 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
> *
>
Powered by blists - more mailing lists