[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <170026757145.1646674.10200174783594509637.b4-ty@kernel.org>
Date: Sat, 18 Nov 2023 00:32:51 +0000
From: Mark Brown <broonie@...nel.org>
To: Maciej Strozek <mstrozek@...nsource.cirrus.com>
Cc: James Schulman <james.schulman@...rus.com>,
David Rhodes <david.rhodes@...rus.com>,
Liam Girdwood <lgirdwood@...il.com>,
alsa-devel@...a-project.org, patches@...nsource.cirrus.com,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 0/7] ASoC: cs43130: Fixes and improvements
On Fri, 17 Nov 2023 14:13:37 +0000, Maciej Strozek wrote:
> This patchset aims to add minor fixes (first two patches) and
> introduce general improvements to the driver (rest of the patches)
>
> Maciej Strozek (7):
> ASoC: cs43130: Fix the position of const qualifier
> ASoC: cs43130: Fix incorrect frame delay configuration
> ASoC: cs43130: Allow configuration of bit clock and frame inversion
> ASoC: cs43130: Store device in private struct and use it more
> consistently
> ASoC: cs43130: Add handling of ACPI
> ASoC: cs43130: Allow driver to work without IRQ thread
> ASoC:cs43130: Add switch to control normal and alt hp inputs
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: cs43130: Fix the position of const qualifier
commit: e7f289a59e76a5890a57bc27b198f69f175f75d9
[2/7] ASoC: cs43130: Fix incorrect frame delay configuration
commit: aa7e8e5e4011571022dc06e4d7a2f108feb53d1a
[3/7] ASoC: cs43130: Allow configuration of bit clock and frame inversion
(no commit info)
[4/7] ASoC: cs43130: Store device in private struct and use it more consistently
commit: 552206add94dd7977bad32c37eba16e23756a0f9
[5/7] ASoC: cs43130: Add handling of ACPI
commit: ce7944b73e7729dc702b6741cff2b26886bb723c
[7/7] ASoC:cs43130: Add switch to control normal and alt hp inputs
commit: 9158221bf2aa5f7bfb916452c079b2fe63ca76e8
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