mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Omer PALA <palaomer100@gmail.com>
Cc: Vaibhav Hiremath <hvaibhav.linux@gmail.com>,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	Vaibhav Agarwal <vaibhav.sr@gmail.com>,
	Mark Greer <mgreer@animalcreek.com>,
	Viresh Kumar <vireshk@kernel.org>,
	Rui Miguel Silva <rmfrfs@gmail.com>,
	Bryan O'Donoghue <pure.logic@nexus-software.ie>,
	David Lin <dtwlin@gmail.com>,
	"moderated list:GREYBUS SUBSYSTEM" <greybus-dev@lists.linaro.org>,
	"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: greybus: change mutexes to guard macros
Date: Sun, 20 Sep 2026 12:11:27 +0200	[thread overview]
Message-ID: <2026092039-greedily-jailer-80e5@gregkh> (raw)
In-Reply-To: <20260920094058.9664-1-palaomer100@gmail.com>

On Sun, Sep 20, 2026 at 12:40:54PM +0300, Omer PALA wrote:
> Convert mutex_lock()/mutex_unlock() pairs to the guard() and
> scoped_guard() cleanup helpers where possible. This removes
> error-prone goto-based unlock paths and makes it harder to
> forget to release a mutex on an early return.
> 
> Signed-off-by: Omer PALA <palaomer100@gmail.com>

Did you miss the review comments I made for the previous patch like this
a few hours ago:
	https://lore.kernel.org/all/2026092014-despair-secular-d579@gregkh/
?

  reply	other threads:[~2026-09-20 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20  9:40 Omer PALA
2026-09-20 10:11 ` Greg Kroah-Hartman [this message]
2026-09-20 10:37   ` Omer PALA
2026-09-20 11:59     ` Bradley Morgan
2026-09-20 12:37     ` Greg Kroah-Hartman
2026-09-20 13:22     ` Krzysztof Kozlowski
2026-09-20 13:26       ` Krzysztof Kozlowski
2026-09-20 18:29         ` Ömer PALA

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=2026092039-greedily-jailer-80e5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dtwlin@gmail.com \
    --cc=elder@kernel.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=hvaibhav.linux@gmail.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mgreer@animalcreek.com \
    --cc=palaomer100@gmail.com \
    --cc=pure.logic@nexus-software.ie \
    --cc=rmfrfs@gmail.com \
    --cc=vaibhav.sr@gmail.com \
    --cc=vireshk@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®