From: "Arnd Bergmann" <arnd@arndb.de>
To: "Dan Carpenter" <dan.carpenter@linaro.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Shenwei Wang" <shenwei.wang@nxp.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Marek Vasut" <marex@denx.de>, "Marc Zyngier" <maz@kernel.org>,
"Dan Carpenter" <error27@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: mxc: fix unused function warnings
Date: Wed, 19 Jul 2023 13:26:06 +0200 [thread overview]
Message-ID: <3e7dbbf3-351c-430e-9bfe-a9e9e9cb895c@app.fastmail.com> (raw)
In-Reply-To: <319ee5f7-2dbd-430d-8ab1-a7b072ac7a9f@kadam.mountain>
On Wed, Jul 19, 2023, at 11:44, Dan Carpenter wrote:
> On Tue, Jul 18, 2023 at 09:39:08PM +0200, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> The new runtime PM support causes a harmless warning about
>> unused functions when runtime PM is disabled:
>>
>> drivers/gpio/gpio-mxc.c:612:12: error: 'mxc_gpio_runtime_resume' defined but not used [-Werror=unused-function]
>> drivers/gpio/gpio-mxc.c:602:12: error: 'mxc_gpio_runtime_suspend' defined but not used [-Werror=unused-function]
>>
>> Change the driver to use the more modern helper macros that avoid these
>> warnings, and remove the now unnecessary __maybe_unused annotations
>>
>> Fixes: 3283d820dce64 ("gpio: mxc: add runtime pm support")
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> ---
>
> The patch is nice, but I don't understand why __maybe_unused doesn't
> work?
Adding __maybe_unused to both mxc_gpio_runtime_resume and
mxc_gpio_runtime_suspend would avoid the warning, and that is
what we used to do in the past before we had the new macros,
including for the mxc_gpio_noirq_suspend/mxc_gpio_noirq_resume
functions in this driver.
Since I'm moving the driver to the new method, it's best to
do it for both pairs of PM functions at the same time, so
the __maybe_unused annotation becomes redundant.
Arnd
next prev parent reply other threads:[~2023-07-19 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 19:39 Arnd Bergmann
2023-07-18 19:54 ` Andy Shevchenko
2023-07-19 9:44 ` Dan Carpenter
2023-07-19 11:26 ` Arnd Bergmann [this message]
2023-07-19 11:30 ` Dan Carpenter
2023-07-20 15:23 ` Bartosz Golaszewski
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=3e7dbbf3-351c-430e-9bfe-a9e9e9cb895c@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=arnd@kernel.org \
--cc=brgl@bgdev.pl \
--cc=dan.carpenter@linaro.org \
--cc=error27@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=maz@kernel.org \
--cc=shenwei.wang@nxp.com \
/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®