From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Wolfram Sang <wsa@kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] i2c: core: Improve i2c_new_scanned_device
Date: Thu, 9 Jan 2025 11:27:44 +0100 [thread overview]
Message-ID: <Z3-koEmVAGPCtV7z@shikoro> (raw)
In-Reply-To: <f4110289-f7e9-471a-bb91-941c85bfb43e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
On Tue, Jan 07, 2025 at 09:29:07PM +0100, Heiner Kallweit wrote:
> Simplify the logic in this function. And as we're no longer limited to
> C89, move the iterator variable declaration to the for loop.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Did you have HW to test this patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-09 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 20:29 [PATCH] i2c: core: Improve i2c_new_scanned_device Heiner Kallweit
2025-01-09 10:27 ` Wolfram Sang [this message]
2025-01-09 13:58 ` Heiner Kallweit
2025-01-14 12:11 ` Wolfram Sang
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=Z3-koEmVAGPCtV7z@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=hkallweit1@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@kernel.org \
/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).