From: <Nicolas.Ferre@microchip.com>
To: <axel.lin@ingics.com>, <broonie@kernel.org>
Cc: <Andrei.Stefanescu@microchip.com>, <lgirdwood@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <Claudiu.Beznea@microchip.com>,
<Ludovic.Desroches@microchip.com>
Subject: Re: [PATCH] regulator: mcp16502: Use #ifdef CONFIG_PM_SLEEP around mcp16502_suspend/resume_noirq
Date: Fri, 21 Dec 2018 11:17:50 +0000 [thread overview]
Message-ID: <3751abc0-1377-2a66-3fa9-7ceee93b7aab@microchip.com> (raw)
In-Reply-To: <20181220131413.21922-1-axel.lin@ingics.com>
On 20/12/2018 at 14:14, Axel Lin wrote:
> mcp16502_suspend/resume_noirq is only used by SET_NOIRQ_SYSTEM_SLEEP_PM_OPS
> when CONFIG_PM_SLEEP is defined.
> So use #ifdef CONFIG_PM_SLEEP instead CONFIG_SUSPEND guard.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
I'm not against this patch and don't know the habits about this... one
remark below...
> ---
> This patch replaces below patch I sent today.
> regulator: mcp16502: Fix build error when !CONFIG_SUSPEND && CONFIG_PM_SLEEP
> Changed the subject line because after commit 308144ce8e51 ("regulator: mcp16502: code cleanup")
> it's not related to build error now.
>
> drivers/regulator/mcp16502.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/regulator/mcp16502.c b/drivers/regulator/mcp16502.c
> index 809a664733a4..cb11fb206899 100644
> --- a/drivers/regulator/mcp16502.c
> +++ b/drivers/regulator/mcp16502.c
> @@ -497,7 +497,7 @@ static int mcp16502_probe(struct i2c_client *client,
> return 0;
> }
>
> -#ifdef CONFIG_SUSPEND
> +#ifdef CONFIG_PM_SLEEP
Why not use CONFIG_PM just like ...
> static int mcp16502_suspend_noirq(struct device *dev)
> {
> struct i2c_client *client = to_i2c_client(dev);
> @@ -517,10 +517,7 @@ static int mcp16502_resume_noirq(struct device *dev)
>
> return 0;
> }
> -#else /* !CONFIG_SUSPEND */
> -#define mcp16502_suspend_noirq NULL
> -#define mcp16502_resume_noirq NULL
> -#endif /* !CONFIG_SUSPEND */
> +#endif
>
> #ifdef CONFIG_PM
... here.... or unify both directives to "CONFIG_PM_SLEEP" ?
Otherwise, no problem in adding my:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
(as Andrei is not with Microchip anymore).
> static const struct dev_pm_ops mcp16502_pm_ops = {
>
--
Nicolas Ferre
prev parent reply other threads:[~2018-12-21 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 13:14 Axel Lin
2018-12-21 11:17 ` Nicolas.Ferre [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=3751abc0-1377-2a66-3fa9-7ceee93b7aab@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Andrei.Stefanescu@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®