From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Conor Dooley <conor+dt@kernel.org>,
Harshal Gohel <hg@simonwunderlich.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Markus Stockhausen <markus.stockhausen@gmx.de>,
Rob Herring <robh@kernel.org>,
Sven Eckelmann <sven@narfation.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH v6 10/12] i2c: rtl9300: use scoped guard instead of explicit lock/unlock
Date: Sun, 24 Aug 2025 19:44:51 +0200 [thread overview]
Message-ID: <44c2cab3-6dcb-4775-9396-a8d9754fdbd4@gmail.com> (raw)
In-Reply-To: <95e31ebe-08d8-4b04-a624-f0ecb8a57d3f@web.de>
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
next prev parent reply other threads:[~2025-08-24 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 11:33 [PATCH v6 00/12] i2c: fix, rework and extend RTL9300 I2C driver Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 01/12] i2c: rtl9300: fix channel number bound check Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 02/12] i2c: rtl9300: ensure data length is within supported range Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 03/12] i2c: rtl9300: remove broken SMBus Quick operation support Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 04/12] i2c: rtl9300: use regmap fields and API for registers Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 05/12] dt-bindings: i2c: realtek,rtl9301-i2c: fix wording and typos Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 06/12] i2c: rtl9300: rename internal sda_pin to sda_num Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 07/12] i2c: rtl9300: move setting SCL frequency to config_io Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 08/12] i2c: rtl9300: do not set read mode on every transfer Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 09/12] i2c: rtl9300: separate xfer configuration and execution Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 10/12] i2c: rtl9300: use scoped guard instead of explicit lock/unlock Jonas Jelonek
2025-08-24 14:12 ` Markus Elfring
2025-08-24 17:44 ` Jonas Jelonek [this message]
2025-08-24 11:33 ` [PATCH v6 11/12] dt-bindings: i2c: realtek,rtl9301-i2c: extend for RTL9310 support Jonas Jelonek
2025-08-24 11:33 ` [PATCH v6 12/12] i2c: rtl9300: add support for RTL9310 I2C controller Jonas Jelonek
2025-08-24 21:31 ` [PATCH v6 00/12] i2c: fix, rework and extend RTL9300 I2C driver Chris Packham
2025-08-25 19:33 ` AW: " markus.stockhausen
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=44c2cab3-6dcb-4775-9396-a8d9754fdbd4@gmail.com \
--to=jelonek.jonas@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=andi.shyti@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hg@simonwunderlich.de \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
--cc=robh@kernel.org \
--cc=sven@narfation.org \
--cc=wsa+renesas@sang-engineering.com \
/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;
as well as URLs for NNTP newsgroup(s).