linux-kernel - Re: [PATCH v6 10/12] i2c: rtl9300: use scoped guard instead of explicit lock/unlock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <44c2cab3-6dcb-4775-9396-a8d9754fdbd4@gmail.com>
Date: Sun, 24 Aug 2025 19:44:51 +0200
From: Jonas Jelonek <jelonek.jonas@...il.com>
To: Markus Elfring <Markus.Elfring@....de>, linux-i2c@...r.kernel.org,
 devicetree@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, Andi Shyti <andi.shyti@...nel.org>,
 Chris Packham <chris.packham@...iedtelesis.co.nz>,
 Conor Dooley <conor+dt@...nel.org>, Harshal Gohel <hg@...onwunderlich.de>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Markus Stockhausen <markus.stockhausen@....de>, Rob Herring
 <robh@...nel.org>, Sven Eckelmann <sven@...fation.org>,
 Wolfram Sang <wsa+renesas@...g-engineering.com>
Subject: Re: [PATCH v6 10/12] i2c: rtl9300: use scoped guard instead of
 explicit lock/unlock



On 24.08.25 16:12, Markus Elfring wrote:
> …
>> when the guard goes out of scope, instead of explicity lock/unlock. This
> …
>
> explicit? Would such a word be nicer in the next line?

I think I wanted to write 'explicitly' but not sure which variant is better.
Having it in the next line would probably be better, I'll fix this.

> Regards,
> Markus

Regards,
Jonas