[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168927986520.272917.957670510176248765.b4-ty@kernel.org>
Date: Thu, 13 Jul 2023 21:24:25 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>,
Lars-Peter Clausen <lars@...afoo.de>,
Nuno Sá <nuno.sa@...log.com>,
Mark Brown <broonie@...nel.org>
Cc: patches@...nsource.cirrus.com, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/10] ASoC: ad: Update Analog Devices drivers to maple
tree register cache
On Thu, 13 Jul 2023 00:13:49 +0100, Mark Brown wrote:
> The maple tree register cache has now got to feature parity with the
> rbtree cache, there are some different tradeoffs made and it should be a
> better choice for most modern systems. Convert the Analog Devices
> drivers to use the more modern data structure.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/10] ASoC: ad1836: Update to use maple tree register cache
commit: 52beea42d825321a7ded656f14f5672b290dbd16
[02/10] ASoC: ad1980: Update to use maple tree register cache
commit: 625ea9e6d5c4509634b49a8e7436ea3248220e9e
[03/10] ASoC: adau1372: Update to use maple tree register cache
commit: b7fea0e30fbdc4c5cba6edbf5e5b8aabd0a5660a
[04/10] ASoC: adau1373: Update to use maple tree register cache
commit: da27e493ce9394134deecfbecfd46c8836141191
[05/10] ASoC: adau1701: Update to use maple tree register cache
commit: e0e3bb187bfba6ec2a0bd1b7d36fdacb6a8e3010
[06/10] ASoC: adau1761: Update to use maple tree register cache
commit: 97e3b4845d389c8e309e13445bc02ad01fdbda7a
[07/10] ASoC: adau1781: Update to use maple tree register cache
commit: 3841ff1bacccc253c48c2c4a2c5e087dfae4b51e
[08/10] ASoC: adau1977: Update to use maple tree register cache
commit: a0a4cef897b550cf4beaf3fcb1742c3dc895f5f8
[09/10] ASoC: adau7118: Update to use maple tree register cache
commit: c05c32dd82a602e5b75c3e473e55e7b6325a1967
[10/10] ASoC: adav80x: Update to use maple tree register cache
commit: 07e835e35b5dc7e1906e2dbd6d72cb9336846ba6
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
Powered by blists - more mailing lists