From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 2/2] gpio: sim: simplify code with cleanup helpers
Date: Thu, 10 Aug 2023 17:39:32 +0300 [thread overview]
Message-ID: <ZNT2pNW3aPu82vs1@smile.fi.intel.com> (raw)
In-Reply-To: <20230809131442.25524-2-brgl@bgdev.pl>
On Wed, Aug 09, 2023 at 03:14:42PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Use macros defined in linux/cleanup.h to automate resource lifetime
> control in the gpio-simulator.
gpio-sim ?
...
> - mutex_lock(&chip->lock);
> + guard(mutex)(&chip->lock);
I hoped to see somehing like
guard_mutex(...);
But looking into cleanup.h it seems to me that the lock itself on GPIO library
can be defined with respective class, no?
...
> + scoped_guard(mutex, &chip->lock)
> + bitmap_replace(chip->value_map, chip->value_map, bits, mask,
> + gc->ngpio);
Perhaps with {} ?
...
> int ret;
>
> - mutex_lock(&dev->lock);
> + guard(mutex)(&dev->lock);
> +
> pdev = dev->pdev;
> if (pdev)
> ret = sprintf(page, "%s\n", dev_name(&pdev->dev));
> else
> ret = sprintf(page, "gpio-sim.%d\n", dev->id);
> - mutex_unlock(&dev->lock);
>
> return ret;
Now can be
if (...)
return ...
else // if you wish (not needed)
return ...
...
> int ret;
>
> - mutex_lock(&dev->lock);
> + guard(mutex)(&dev->lock);
> +
> if (gpio_sim_device_is_live_unlocked(dev))
> ret = device_for_each_child(&dev->pdev->dev, &ctx,
> gpio_sim_emit_chip_name);
> else
> ret = sprintf(page, "none\n");
> - mutex_unlock(&dev->lock);
>
> return ret;
As per above. And may be other functions as well.
...
> int ret;
>
> - mutex_lock(&dev->lock);
> - ret = sprintf(page, "%s\n", line->name ?: "");
> - mutex_unlock(&dev->lock);
> + scoped_guard(mutex, &dev->lock)
> + ret = sprintf(page, "%s\n", line->name ?: "");
>
> return ret;
Why not
guard(...);
return sprintf(...);
?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-10 14:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:14 [PATCH 1/2] gpio: sim: use sysfs_streq() and avoid an strdup() Bartosz Golaszewski
2023-08-09 13:14 ` [PATCH 2/2] gpio: sim: simplify code with cleanup helpers Bartosz Golaszewski
2023-08-10 14:39 ` Andy Shevchenko [this message]
2023-08-10 19:04 ` Bartosz Golaszewski
2023-08-11 9:14 ` Andy Shevchenko
2023-08-11 12:42 ` Bartosz Golaszewski
2023-08-11 5:20 ` Dan Carpenter
2023-08-11 9:14 ` Andy Shevchenko
2023-08-11 9:31 ` Dan Carpenter
2023-08-15 8:04 ` Linus Walleij
2023-08-15 15:52 ` Peter Zijlstra
2023-08-15 15:58 ` Andy Shevchenko
2023-08-15 20:31 ` Peter Zijlstra
2023-08-16 12:47 ` Peter Zijlstra
2023-08-17 9:21 ` Andy Shevchenko
2023-08-10 14:04 ` [PATCH 1/2] gpio: sim: use sysfs_streq() and avoid an strdup() Andy Shevchenko
2023-08-11 11:59 ` 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=ZNT2pNW3aPu82vs1@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.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