public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Menderes Sabaz <sabazmenderes@gmail.com>
Cc: Michael.Hennerich@analog.com, andy@kernel.org,
	dlechner@baylibre.com, lars@metafoo.de,
	linux-iio@vger.kernel.org, nuno.sa@analog.com
Subject: Re: [PATCH v2] iio: dac: ad5360: convert to guard(mutex)
Date: Thu, 29 Jan 2026 16:18:48 +0000	[thread overview]
Message-ID: <20260129161848.49b8a226@jic23-huawei> (raw)
In-Reply-To: <20260129161621.7900dc11@jic23-huawei>

On Thu, 29 Jan 2026 16:16:21 +0000
Jonathan Cameron <jic23@kernel.org> wrote:

> On Wed, 28 Jan 2026 18:32:21 +0300
> Menderes Sabaz <sabazmenderes@gmail.com> wrote:
> 
> > Converting mutex_lock and mutex_unlock to guard(mutex)
> > Simplify the locking logic by using guard(mutex).
> > This removes the need for explicit unlock calls in error paths and
> > simplifies the code by removing goto labels.
> > 
> > Signed-off-by: Menderes Sabaz <sabazmenderes@gmail.com>  
> 
> Hi Menderes,
> 
> Applied to the togreg branch of iio.git.
Dropped again.  For some reason my local email hadn't picked up
the rest of the discussion and I only noticed when I looked at patchwork.

> 
> Thanks,
> 
> Jonathan
> 


      reply	other threads:[~2026-01-29 16:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 11:37 [PATCH] iio: dac: ad5360: convert to guard(mutex) Menderes Sabaz
2026-01-28 14:54 ` David Lechner
2026-01-28 15:32 ` [PATCH v2] " Menderes Sabaz
2026-01-28 22:32   ` Andy Shevchenko
2026-01-28 22:47   ` David Lechner
2026-01-28 23:14   ` [PATCH] iio: dac: ad5360: converting " Menderes Sabaz
2026-01-29 10:54     ` Andy Shevchenko
2026-01-29 16:16   ` [PATCH v2] iio: dac: ad5360: convert " Jonathan Cameron
2026-01-29 16:18     ` Jonathan Cameron [this message]

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=20260129161848.49b8a226@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=sabazmenderes@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