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:     ckeepax@opensource.cirrus.com
Cc:     david.rhodes@cirrus.com, linux-kernel@vger.kernel.org,
        patches@opensource.cirrus.com, james.schulman@cirrus.com,
        lgirdwood@gmail.com, alsa-devel@alsa-project.org
In-Reply-To: <20220621102041.1713504-1-ckeepax@opensource.cirrus.com>
References: <20220621102041.1713504-1-ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH 1/4] ASoC: wm_adsp: Fix event for preloader
Message-Id: <165583076515.271995.18026911532153153999.b4-ty@kernel.org>
Date:   Tue, 21 Jun 2022 17:59:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 21 Jun 2022 11:20:38 +0100, Charles Keepax wrote:
> The preloader controls on ADSP should return a value of 1 if the
> preloader value was changed, update to correct this.
> 
> 

Applied to

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

Thanks!

[1/4] ASoC: wm_adsp: Fix event for preloader
      commit: 81d74ddae83fbd85c9006835f36c362114127a7a
[2/4] ASoC: wm5110: Fix DRE control
      commit: 630cc5983740d784a1a6458f9dc2112c43fe0931
[3/4] ASoC: cs35l41: Correct some control names
      commit: 87912e97a1678d62877aab353ecfd201bc92b372
[4/4] ASoC: core: Add new SOC_DOUBLE_SX_TLV macro
      commit: 6b183919f7051294dc5fc331bb608d5d7f29f5da

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