From: Mark Brown <broonie@kernel.org>
To: "Liam Girdwood" <lgirdwood@gmail.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Nuno Sá" <nuno.sa@analog.com>, "Mark Brown" <broonie@kernel.org>
Cc: patches@opensource.cirrus.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] ASoC: ad: Update Analog Devices drivers to maple tree register cache
Date: Thu, 13 Jul 2023 21:24:25 +0100 [thread overview]
Message-ID: <168927986520.272917.957670510176248765.b4-ty@kernel.org> (raw)
In-Reply-To: <20230713-asoc-ad-maple-v1-0-7d2f35d42b5f@kernel.org>
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
prev parent reply other threads:[~2023-07-13 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 23:13 [PATCH 00/10] ASoC: ad: Update Analog Devices drivers to maple tree register cache Mark Brown
2023-07-12 23:13 ` [PATCH 01/10] ASoC: ad1836: Update to use " Mark Brown
2023-07-12 23:13 ` [PATCH 02/10] ASoC: ad1980: " Mark Brown
2023-07-12 23:13 ` [PATCH 03/10] ASoC: adau1372: " Mark Brown
2023-07-12 23:13 ` [PATCH 04/10] ASoC: adau1373: " Mark Brown
2023-07-12 23:13 ` [PATCH 05/10] ASoC: adau1701: " Mark Brown
2023-07-12 23:13 ` [PATCH 06/10] ASoC: adau1761: " Mark Brown
2023-07-12 23:13 ` [PATCH 07/10] ASoC: adau1781: " Mark Brown
2023-07-12 23:13 ` [PATCH 08/10] ASoC: adau1977: " Mark Brown
2023-07-12 23:13 ` [PATCH 09/10] ASoC: adau7118: " Mark Brown
2023-07-12 23:13 ` [PATCH 10/10] ASoC: adav80x: " Mark Brown
2023-07-13 7:02 ` [PATCH 00/10] ASoC: ad: Update Analog Devices drivers to " Nuno Sá
2023-07-13 20:24 ` 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=168927986520.272917.957670510176248765.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.