From: Andrew Davis <afd@ti.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
<linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpio: pisosr: Use devm_mutex_init()
Date: Sun, 7 Sep 2025 09:09:57 -0500 [thread overview]
Message-ID: <7dc4da15-28a4-4e1f-b0c9-9115f97edd77@ti.com> (raw)
In-Reply-To: <01910ebdaba7d8d0cdc4ac60eb70da8e29cb85f1.1757251512.git.christophe.jaillet@wanadoo.fr>
On 9/7/25 8:25 AM, Christophe JAILLET wrote:
> Use devm_mutex_init() instead of hand-writing it.
>
> This saves some LoC, improves readability and saves some space in the
> generated .o file.
>
> Before:
> ======
> text data bss dec hex filename
> 8431 1808 192 10431 28bf drivers/gpio/gpio-pisosr.o
>
> After:
> =====
> text data bss dec hex filename
> 8112 1736 192 10040 2738 drivers/gpio/gpio-pisosr.o
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
Acked-by: Andrew Davis <afd@ti.com>
> drivers/gpio/gpio-pisosr.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/gpio/gpio-pisosr.c b/drivers/gpio/gpio-pisosr.c
> index a69b74866a13..7ec6a46ed600 100644
> --- a/drivers/gpio/gpio-pisosr.c
> +++ b/drivers/gpio/gpio-pisosr.c
> @@ -108,11 +108,6 @@ static const struct gpio_chip template_chip = {
> .can_sleep = true,
> };
>
> -static void pisosr_mutex_destroy(void *lock)
> -{
> - mutex_destroy(lock);
> -}
> -
> static int pisosr_gpio_probe(struct spi_device *spi)
> {
> struct device *dev = &spi->dev;
> @@ -139,8 +134,7 @@ static int pisosr_gpio_probe(struct spi_device *spi)
> return dev_err_probe(dev, PTR_ERR(gpio->load_gpio),
> "Unable to allocate load GPIO\n");
>
> - mutex_init(&gpio->lock);
> - ret = devm_add_action_or_reset(dev, pisosr_mutex_destroy, &gpio->lock);
> + ret = devm_mutex_init(dev, &gpio->lock);
> if (ret)
> return ret;
>
next prev parent reply other threads:[~2025-09-07 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 13:25 Christophe JAILLET
2025-09-07 14:09 ` Andrew Davis [this message]
2025-09-08 7:38 ` 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=7dc4da15-28a4-4e1f-b0c9-9115f97edd77@ti.com \
--to=afd@ti.com \
--cc=brgl@bgdev.pl \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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®