From: Wolfram Sang <wsa@kernel.org>
To: Stephen Kitt <steve@sk2.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 01/10] clk: cdce706: use simple i2c probe function
Date: Thu, 7 Apr 2022 22:15:24 +0200 [thread overview]
Message-ID: <Yk9GXDF5MOF574CG@shikoro> (raw)
In-Reply-To: <20220407151831.2371706-11-steve@sk2.org> <20220407151831.2371706-10-steve@sk2.org> <20220407151831.2371706-9-steve@sk2.org> <20220407151831.2371706-8-steve@sk2.org> <20220407151831.2371706-7-steve@sk2.org> <20220407151831.2371706-6-steve@sk2.org> <20220407151831.2371706-5-steve@sk2.org> <20220407151831.2371706-4-steve@sk2.org> <20220407151831.2371706-3-steve@sk2.org> <20220407151831.2371706-2-steve@sk2.org>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
On Thu, Apr 07, 2022 at 05:18:22PM +0200, Stephen Kitt wrote:
> The i2c probe function here doesn't use the id information provided in
> its second argument, so the single-parameter i2c probe function
> ("probe_new") can be used instead.
>
> This avoids scanning the identifier tables during probes.
>
> Signed-off-by: Stephen Kitt <steve@sk2.org>
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-07 20:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 15:18 [PATCH v2 00/10] clk: switch to simple i2c probe function Stephen Kitt
2022-04-07 15:18 ` [PATCH v2 01/10] clk: cdce706: use " Stephen Kitt
2022-04-07 20:09 ` Wolfram Sang
2022-04-07 20:15 ` Wolfram Sang [this message]
2022-04-23 2:32 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 02/10] clk: cdce925: use i2c_match_id and simple i2c probe Stephen Kitt
2022-04-07 20:13 ` Wolfram Sang
2022-04-23 2:32 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 03/10] clk: cs2000-cp: use simple i2c probe function Stephen Kitt
2022-04-07 20:14 ` Wolfram Sang
2022-04-23 2:32 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 04/10] clk: max9485: " Stephen Kitt
2022-04-07 20:14 ` Wolfram Sang
2022-04-23 2:33 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 05/10] clk: si514: " Stephen Kitt
2022-04-07 20:14 ` Wolfram Sang
2022-04-23 2:33 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 06/10] clk: si5341: " Stephen Kitt
2022-04-07 20:14 ` Wolfram Sang
2022-04-23 2:33 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 07/10] clk: si5351: use i2c_match_id and simple i2c probe Stephen Kitt
2022-04-07 20:18 ` Wolfram Sang
2022-04-23 2:34 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 08/10] clk: si544: " Stephen Kitt
2022-04-07 20:19 ` Wolfram Sang
2022-04-23 2:34 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 09/10] clk: si570: " Stephen Kitt
2022-04-07 20:19 ` Wolfram Sang
2022-04-23 2:35 ` Stephen Boyd
2022-04-07 15:18 ` [PATCH v2 10/10] clk: renesas-pcie: use simple i2c probe function Stephen Kitt
2022-04-07 20:19 ` Wolfram Sang
2022-04-23 2:35 ` Stephen Boyd
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=Yk9GXDF5MOF574CG@shikoro \
--to=wsa@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=steve@sk2.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