Re: [PATCH] staging: nvec: use guard(mutex) in nvec_write_sync()

[Jeremy Clifton <deaner92@yahoo.com>]

Hi T Obabi,

On 10/13/26 4:58 PM, Temitope Obabi wrote:
> Hi I have finally installed Ubuntu on my system, I hope am on the right 
> track
You need to send plain text.
Also, there is no need to reply to my v2 message here. Reply to the 
Welcome 2026 Applicants. If you don't have that email, send out to 
outreachy@lists.linux.dev with an intro.

Look into plain text. >
> On Tue, 13 Oct 2026, 7:57 pm Thierry Reding, <thierry.reding@kernel.org 
> <mailto:thierry.reding@kernel.org>> wrote:
> 
>     On Mon, Oct 12, 2026 at 03:41:48PM -0600, 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?
> 
>     Not a big deal in this case, but you might want to read up on how to
>     properly reply to emails:
> 
>     https://subspace.kernel.org/etiquette.html#do-not-top-post-when-
>     replying <https://subspace.kernel.org/etiquette.html#do-not-top-
>     post-when-replying>
> 
>     Thierry
>