From: Mark Brown <broonie@kernel.org>
To: "Lars-Peter Clausen" <lars@metafoo.de>,
"Nuno Sá" <nuno.sa@analog.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Marek Vasut" <marex@denx.de>, "Andrew Davis" <afd@ti.com>
Cc: patches@opensource.cirrus.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/21] ASoC: ad193x: Remove use of i2c_match_id()
Date: Tue, 10 Dec 2024 13:00:20 +0000 [thread overview]
Message-ID: <173383562098.33694.17429584672866095878.b4-ty@kernel.org> (raw)
In-Reply-To: <20241203200001.197295-1-afd@ti.com>
On Tue, 03 Dec 2024 13:59:41 -0600, Andrew Davis wrote:
> The function i2c_match_id() is used to fetch the matching ID from
> the i2c_device_id table. This is often used to then retrieve the
> matching driver_data. This can be done in one step with the helper
> i2c_get_match_data().
>
> This helper has a couple other benefits:
> * It doesn't need the i2c_device_id passed in so we do not need
> to have that forward declared, allowing us to remove those or
> move the i2c_device_id table down to its more natural spot
> with the other module info.
> * It also checks for device match data, which allows for OF and
> ACPI based probing. That means we do not have to manually check
> those first and can remove those checks.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/21] ASoC: ad193x: Remove use of i2c_match_id()
commit: 8c491103c946fb760005044a74c82d7cf6c6f6b4
[02/21] ASoC: adau1761: Remove use of i2c_match_id()
commit: 56731c80fc3b17850e49913cec262c2bcaa88dcb
[03/21] ASoC: adau1781: Remove use of i2c_match_id()
commit: f9812846ffdb1f5686154cae18ca8cc765232967
[04/21] ASoC: adau1977: Remove use of i2c_match_id()
commit: d6ba6f50fae4170a8b7058da81dc2644913a5216
[05/21] ASoC: alc5623: Remove use of i2c_match_id()
commit: b5e8f7abbb73d0f71ec8742c990c7e1ffa44a554
[06/21] ASoC: alc5632: Remove use of i2c_match_id()
commit: 99816f3fa964380a50ccc898b08cc7d9dd58c764
[07/21] ASoC: max98088: Remove use of i2c_match_id()
commit: ebf572bfefcd27584e1b32b0dd51ba71f3fe33d6
[08/21] ASoC: max98090: Remove use of i2c_match_id()
commit: db2aaa0943803fbba606e3b59b5cf900eced2a5c
[09/21] ASoC: max98095: Remove use of i2c_match_id()
commit: a8bb9855de4c5ca5b586814b7f8cc4a77d9e8b9c
[10/21] ASoC: pcm186x: Remove use of i2c_match_id()
commit: b9f99efcc59ae86bcf238719e29427e9519b3878
[11/21] ASoc: pcm6240: Remove use of i2c_match_id()
commit: 0a7bd3dba60a967032ce8c05b4d81350f01ecc8a
[12/21] ASoC: ssm2602: Remove use of i2c_match_id()
commit: 6c978c1baeb8449114e8cb35c68832e903f713d8
[13/21] ASoC: tas2562: Remove use of i2c_match_id()
commit: eb4b5da0ecf61135533574285bacb9dab4fc4703
[14/21] ASoC: tas2781: Remove use of i2c_match_id()
commit: af4cffb250ec9e26a76c90cf753f1a6630811eed
[15/21] ASoC: tas5720: Remove use of i2c_match_id()
commit: 06c61070173803a5341be31ff5281d15cc133e5d
[16/21] ASoC: tlv320adc3xxx: Remove use of i2c_match_id()
commit: 55cf63cc8d951246ec35195ae5a1628beb9c9da3
[17/21] ASoC: tlv320aic31xx: Remove use of i2c_match_id()
commit: f742875ee2534473ca4bf5ce1e120bebdf8d624d
[18/21] ASoC: tlv320aic3x: Remove use of i2c_match_id()
commit: 2a169c459d9614dd6edebd8d34ab096b09f134ac
[19/21] ASoC: tpa6130a2: Remove use of i2c_match_id()
commit: cb47dcedef8dee9e9e64598612b2a301f70a7fdb
[20/21] ASoC: wm8904: Remove use of i2c_match_id()
commit: 77f3bfeacb939b47e1ffcda000cdf3c52af70e0f
[21/21] ASoC: wm8985: Remove use of i2c_match_id()
commit: 7d57d1ce9398bb59fa0b251aa2ffa6eafef5cff4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2024-12-10 13:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 19:59 Andrew Davis
2024-12-03 19:59 ` [PATCH 02/21] ASoC: adau1761: " Andrew Davis
2024-12-03 19:59 ` [PATCH 03/21] ASoC: adau1781: " Andrew Davis
2024-12-03 19:59 ` [PATCH 04/21] ASoC: adau1977: " Andrew Davis
2024-12-03 19:59 ` [PATCH 05/21] ASoC: alc5623: " Andrew Davis
2024-12-03 19:59 ` [PATCH 06/21] ASoC: alc5632: " Andrew Davis
2024-12-03 19:59 ` [PATCH 07/21] ASoC: max98088: " Andrew Davis
2024-12-03 19:59 ` [PATCH 08/21] ASoC: max98090: " Andrew Davis
2024-12-03 19:59 ` [PATCH 09/21] ASoC: max98095: " Andrew Davis
2024-12-03 19:59 ` [PATCH 10/21] ASoC: pcm186x: " Andrew Davis
2024-12-03 19:59 ` [PATCH 11/21] ASoc: pcm6240: " Andrew Davis
2024-12-03 19:59 ` [PATCH 12/21] ASoC: ssm2602: " Andrew Davis
2024-12-03 19:59 ` [PATCH 13/21] ASoC: tas2562: " Andrew Davis
2024-12-03 19:59 ` [PATCH 14/21] ASoC: tas2781: " Andrew Davis
2024-12-03 19:59 ` [PATCH 15/21] ASoC: tas5720: " Andrew Davis
2024-12-03 19:59 ` [PATCH 16/21] ASoC: tlv320adc3xxx: " Andrew Davis
2024-12-03 19:59 ` [PATCH 17/21] ASoC: tlv320aic31xx: " Andrew Davis
2024-12-03 19:59 ` [PATCH 18/21] ASoC: tlv320aic3x: " Andrew Davis
2024-12-03 19:59 ` [PATCH 19/21] ASoC: tpa6130a2: " Andrew Davis
2024-12-03 20:00 ` [PATCH 20/21] ASoC: wm8904: " Andrew Davis
2024-12-05 13:39 ` Charles Keepax
2024-12-03 20:00 ` [PATCH 21/21] ASoC: wm8985: " Andrew Davis
2024-12-05 13:39 ` Charles Keepax
2024-12-10 13:00 ` Mark Brown [this message]
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=173383562098.33694.17429584672866095878.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=afd@ti.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=marex@denx.de \
--cc=nuno.sa@analog.com \
--cc=patches@opensource.cirrus.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
all inboxes | Powered by JetHome®