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:     Richard Fitzgerald <rf@opensource.cirrus.com>
Cc:     alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
        patches@opensource.cirrus.com
In-Reply-To: <20230808164702.21272-1-rf@opensource.cirrus.com>
References: <20230808164702.21272-1-rf@opensource.cirrus.com>
Subject: Re: [PATCH 0/5] ASoC: cs35l56: Bugfixes
Message-Id: <169160201427.157618.11759081939312972339.b4-ty@kernel.org>
Date:   Wed, 09 Aug 2023 18:26:54 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 08 Aug 2023 17:46:57 +0100, Richard Fitzgerald wrote:
> Miscellaneous bugfixes for the cs35l56 codec driver.
> 
> Richard Fitzgerald (3):
>   ASoC: cs35l56: Avoid uninitialized variable in
>     cs35l56_set_asp_slot_positions()
>   ASoC: cs35l56: Don't rely on GPIOD_OUT_LOW to set RESET initially low
>   ASoC: cs35l56: Wait for control port ready during system-resume
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: cs35l56: Avoid uninitialized variable in cs35l56_set_asp_slot_positions()
      commit: ebd0f7b08e032900e5327962f7da6bed6f37feb6
[2/5] ASoC: cs35l56: Don't rely on GPIOD_OUT_LOW to set RESET initially low
      commit: 853734588dcb1bf4c41a17e4d9df231965e559db
[3/5] ASoC: cs35l56: Wait for control port ready during system-resume
      commit: f5eb9503e80e70c22e3d3f73a5d3c149c132407f
[4/5] ASoC: wm_adsp: Expose the DSP power down actions as wm_adsp_power_down()
      commit: d0a3a6ad0d3b24578f1b3832ad1d7fbdb20f7a20
[5/5] ASoC: cs35l56: Call wm_adsp_power_down() before reloading firmware
      commit: e24ef967c735bf7272099610e422f964c0a4258b

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