From: Paul Cercueil <paul@crapouillou.net>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 13/28] mfd: sec: Remove #ifdef guards for PM related functions
Date: Mon, 08 Aug 2022 12:14:15 +0200 [thread overview]
Message-ID: <RFKAGR.U6QGSG9SKKVK3@crapouillou.net> (raw)
In-Reply-To: <e4dbc605-e998-dbca-b9bc-322783578564@linaro.org>
[...]
>>>> ---
>>>> drivers/mfd/sec-core.c | 7 +++----
>>>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git a/drivers/mfd/sec-core.c b/drivers/mfd/sec-core.c
>>>> index 1fb29c45f5cf..a467de2b2fea 100644
>>>> --- a/drivers/mfd/sec-core.c
>>>> +++ b/drivers/mfd/sec-core.c
>>>> @@ -455,7 +455,6 @@ static void sec_pmic_shutdown(struct
>>>> i2c_client
>>>> *i2c)
>>>> regmap_update_bits(sec_pmic->regmap_pmic, reg, mask, 0);
>>>> }
>>>>
>>>> -#ifdef CONFIG_PM_SLEEP
>>>> static int sec_pmic_suspend(struct device *dev)
>>>
>>> Did you test W=1 with !CONFIG_PM_SLEEP? No warnings?
>>
>> I tested the PR with !CONFIG_PM_SLEEP, correct. sec-core.o compiles
>> fine. No warnings with W=1.
>
> Ah, I see now. _DEFINE_DEV_PM_OPS uses __maybe_unused for such case.
Actually it doesn't :) Since the (dev_pm_ops) structure is always (and
should always be) referenced through pm_sleep_ptr() or pm_ptr(), the
symbols are never seen as unused by the compiler, but are automatically
dropped by the compiler when the related config option is turned off.
Cheers,
-Paul
next prev parent reply other threads:[~2022-08-08 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220807145247.46107-1-paul@crapouillou.net>
2022-08-07 14:52 ` [PATCH 13/28] mfd: sec: Remove #ifdef guards for PM related functions Paul Cercueil
2022-08-08 9:11 ` Krzysztof Kozlowski
2022-08-08 9:28 ` Paul Cercueil
2022-08-08 10:06 ` Krzysztof Kozlowski
2022-08-08 10:14 ` Paul Cercueil [this message]
2022-08-09 15:33 ` Lee Jones
2022-08-09 15:51 ` Krzysztof Kozlowski
2022-08-09 17:26 ` Lee Jones
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=RFKAGR.U6QGSG9SKKVK3@crapouillou.net \
--to=paul@crapouillou.net \
--cc=b.zolnierkie@samsung.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@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