From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.cirrus.com,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH 0/3] ASoC: cs35l56: Remove obsolete and redundant code
Date: Tue, 02 Jul 2024 19:03:11 +0100 [thread overview]
Message-ID: <171994339125.996226.7675778991183465328.b4-ty@kernel.org> (raw)
In-Reply-To: <20240701104444.172556-1-rf@opensource.cirrus.com>
On Mon, 01 Jul 2024 11:44:41 +0100, Richard Fitzgerald wrote:
> These commits remove various code that is either no longer needed,
> or is redundant.
>
> Richard Fitzgerald (3):
> ASoC: cs35l56: Revert support for dual-ownership of ASP registers
> ASoC: cs35l56: Remove support for A1 silicon
> ASoC: cs35l56: Remove redundant clearing of clk_stop_mode1
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: cs35l56: Revert support for dual-ownership of ASP registers
commit: 5d7e328e20b3d2bd3e1e8bea7a868ab8892aeed1
[2/3] ASoC: cs35l56: Remove support for A1 silicon
commit: e2996141d6db0d8b353e1c221a37c8e1be109d4a
[3/3] ASoC: cs35l56: Remove redundant clearing of clk_stop_mode1
commit: e5524e3316ac54ca04dde3bfef4565bacf72c594
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-07-02 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 10:44 [PATCH 0/3] ASoC: cs35l56: Remove obsolete and redundant code Richard Fitzgerald
2024-07-01 10:44 ` [PATCH 1/3] ASoC: cs35l56: Revert support for dual-ownership of ASP registers Richard Fitzgerald
2024-07-01 10:44 ` [PATCH 2/3] ASoC: cs35l56: Remove support for A1 silicon Richard Fitzgerald
2024-07-01 10:44 ` [PATCH 3/3] ASoC: cs35l56: Remove redundant clearing of clk_stop_mode1 Richard Fitzgerald
2024-07-02 18:03 ` 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=171994339125.996226.7675778991183465328.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@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