public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kurt Borja" <kuurtb@gmail.com>
To: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Kurt Borja" <kuurtb@gmail.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Benson Leung" <bleung@chromium.org>,
	"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
	"Gwendal Grignou" <gwendal@chromium.org>,
	"Shrikant Raskar" <raskar.shree97@gmail.com>,
	"Per-Daniel Olsson" <perdaniel.olsson@axis.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Guenter Roeck" <groeck@chromium.org>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	chrome-platform@lists.linux.dev
Subject: Re: [PATCH v4 4/7] iio: core: Add cleanup.h support for iio_device_claim_*()
Date: Mon, 19 Jan 2026 14:31:38 -0500	[thread overview]
Message-ID: <DFSTDSO5P9RC.DGCGPD10KYPG@gmail.com> (raw)
In-Reply-To: <aW3oEZ2WSp0JGl90@smile.fi.intel.com>

On Mon Jan 19, 2026 at 3:15 AM -05, Andy Shevchenko wrote:
> On Sun, Jan 18, 2026 at 10:44:31AM -0500, Kurt Borja wrote:
>> Add guard classes for iio_device_claim_*() conditional locks. This will
>> aid drivers write safer and cleaner code when dealing with some common
>> patterns.
>> 
>> These classes are not meant to be used directly by drivers (hence the
>> __priv__ prefix). Instead, documented wrapper macros are provided to
>> enforce the use of ACQUIRE() or guard() semantics and avoid the
>> problematic scoped guard.
>
> Acked-by: Andy Shevchenko <andriy.shevchenko@intel.com>

Hi Andy,

Thank you for your feedback!

-- 
Thanks,
 ~ Kurt

  reply	other threads:[~2026-01-19 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 15:44 [PATCH v4 0/7] iio: core: Introduce cleanup.h support for mode locks Kurt Borja
2026-01-18 15:44 ` [PATCH v4 1/7] iio: core: Add and export __iio_dev_mode_lock() Kurt Borja
2026-01-18 15:44 ` [PATCH v4 2/7] iio: core: Refactor iio_device_claim_direct() implementation Kurt Borja
2026-01-18 15:44 ` [PATCH v4 3/7] iio: core: Match iio_device_claim_*() semantics and implementation Kurt Borja
2026-01-18 15:44 ` [PATCH v4 4/7] iio: core: Add cleanup.h support for iio_device_claim_*() Kurt Borja
2026-01-18 19:35   ` David Lechner
2026-01-19 19:30     ` Kurt Borja
2026-01-19  8:15   ` Andy Shevchenko
2026-01-19 19:31     ` Kurt Borja [this message]
2026-01-18 15:44 ` [PATCH v4 5/7] iio: light: vcnl4000: Use IIO cleanup helpers Kurt Borja
2026-01-18 15:44 ` [PATCH v4 6/7] iio: health: max30102: " Kurt Borja
2026-01-18 15:44 ` [PATCH v4 7/7] iio: light: opt4060: " Kurt Borja

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=DFSTDSO5P9RC.DGCGPD10KYPG@gmail.com \
    --to=kuurtb@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dlechner@baylibre.com \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=perdaniel.olsson@axis.com \
    --cc=raskar.shree97@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