From: Jeremy Clifton <deaner92@yahoo.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Marc Dietrich <marvin24@gmx.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
ac100@lists.launchpad.net, linux-tegra@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: nvec: use guard(mutex) in nvec_write_sync()
Date: Mon, 12 Oct 2026 15:41:48 -0600 [thread overview]
Message-ID: <492e9a13-b50b-48cb-bd41-3114573c7950@yahoo.com> (raw)
In-Reply-To: <b51c3755-a967-3de3-5f8c-3e4984d6e93c@inria.fr>
Thank you so much for your guidance and feedback.
It is the result that the patch will produce. All the unlock calls will
be deleted and the out of memory path will have no braces, as per
the style guidelines.
The motivation behind the patch is to defer usage of manual locks
for new and improved guards, disallowing lock leaks.
This way, there can be no error producing path by not calling unlock.
Shall I send a v2 with motivation included?
On 10/12/26 2:45 PM, Julia Lawall wrote:
> Is this the motivation for
> doing the patch or the result of the patch.
next prev parent reply other threads:[~2026-10-12 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261012171312.5998-1-deaner92.ref@yahoo.com>
2026-10-12 17:13 ` Jeremy Dean Clifton
2026-10-12 20:45 ` Julia Lawall
2026-10-12 21:41 ` Jeremy Clifton [this message]
2026-10-12 21:48 ` Julia Lawall
2026-10-13 16:03 ` Thierry Reding
[not found] ` <CALUk5xZtpOH=23mdiT7MYs-gem2NL+EoV=priVxuSubbCocqFQ@mail.gmail.com>
2026-10-13 23:18 ` Jeremy Clifton
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=492e9a13-b50b-48cb-bd41-3114573c7950@yahoo.com \
--to=deaner92@yahoo.com \
--cc=ac100@lists.launchpad.net \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=outreachy@lists.linux.dev \
/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®