mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Jeremy Clifton <deaner92@yahoo.com>
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 17:48:11 -0400 (EDT)	[thread overview]
Message-ID: <525671bb-35b-32fc-94a6-e4e066fc1966@inria.fr> (raw)
In-Reply-To: <492e9a13-b50b-48cb-bd41-3114573c7950@yahoo.com>



On Mon, 12 Oct 2026, Jeremy Clifton wrote:

> 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?

Please adjust the second sentence to be clear that it is referring to the
result, not the initial state.  If you would like to add something about
the motivation, that would probably be good too.

thanks,
julia

>
> On 10/12/26 2:45 PM, Julia Lawall wrote:
> > Is this the motivation for
> > doing the patch or the result of the patch.
>
>

  reply	other threads:[~2026-10-12 21:48 UTC|newest]

Thread overview: 5+ 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
2026-10-12 21:48       ` Julia Lawall [this message]
2026-10-13 16:03       ` Thierry Reding

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=525671bb-35b-32fc-94a6-e4e066fc1966@inria.fr \
    --to=julia.lawall@inria.fr \
    --cc=ac100@lists.launchpad.net \
    --cc=deaner92@yahoo.com \
    --cc=gregkh@linuxfoundation.org \
    --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®