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:     Charles Keepax <ckeepax@opensource.cirrus.com>
Cc:     lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
        alsa-devel@alsa-project.org, patches@opensource.cirrus.com
In-Reply-To: <20220722094851.92521-1-ckeepax@opensource.cirrus.com>
References: <20220722094851.92521-1-ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH 1/2] firmware: cs_dsp: Add pre_stop callback
Message-Id: <165851877383.1163063.17627437769670549231.b4-ty@kernel.org>
Date:   Fri, 22 Jul 2022 20:39:33 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 22 Jul 2022 10:48:50 +0100, Charles Keepax wrote:
> The code already has a post_stop callback, add a matching pre_stop
> callback to the client_ops that is called before execution is stopped.
> This callback provides a convenient place for the client code to
> communicate with the DSP before it is stopped.
> 
> 

Applied to

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

Thanks!

[1/2] firmware: cs_dsp: Add pre_stop callback
      commit: dea997733575c5793ca77e166bbbf89097987eb4
[2/2] firmware: cs_dsp: Add memory chunk helpers
      commit: a4b976552f122ea851f556769874022cf097741e

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