Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     lgirdwood@gmail.com, steve@sk2.org
Cc:     wsa@kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20220415160613.148882-1-steve@sk2.org>
References: <20220415160613.148882-1-steve@sk2.org>
Subject: Re: [PATCH v2 0/7] ASoC: remaining i2c_match_id i2c probe changes
Message-Id: <165090744431.583823.7165616164947839079.b4-ty@kernel.org>
Date:   Mon, 25 Apr 2022 18:24:04 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 15 Apr 2022 18:06:06 +0200, Stephen Kitt wrote:
> This series covers all the remaining changes to migrate
> sound/soc/codecs i2c probes to probe_new, where the const struct
> i2c_client * argument is still used. Instead of relying on the
> parameter passed in, i2c_match_id is used instead.
> 
> With this set of patches, all the sound/soc/codecs i2c probes use the
> new probe definition.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/7] ASoC: ak*: use i2c_match_id and simple i2c probe
      commit: e654a1331f68550f4c7c85b13b2bdb3c2502a9af
[2/7] ASoC: alc56*: use i2c_match_id and simple i2c probe
      commit: 9d8f2edd3d7d11c9f1fc978e36219b3178af13bc
[3/7] ASoC: max980*: use i2c_match_id and simple i2c probe
      commit: 4ac8ebb6cc28cbd99e10d7a4772be1c4da5af130
[4/7] ASoC: pcm186x: use i2c_match_id and simple i2c probe
      commit: 3577a8a0ac5b9aaf22ff4fa6a9670cf85351ae50
[5/7] ASoC: tas*: use i2c_match_id and simple i2c probe
      commit: 55116b39e5e1c2d0fd1a77e9f46ce8437623e0e8
[6/7] ASoC: tlv320*: use i2c_match_id and simple i2c probe
      commit: 988e6870c86cce7999f55133197fddfe7e2795d2
[7/7] ASoC: tpa6130: use i2c_match_id and simple i2c probe
      (no commit info)

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