Received-SPF: pass (google.com: domain of linux-kernel+bounces-118108-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, alsa-devel@alsa-project.org, 
 linux-kernel@vger.kernel.org, patches@opensource.cirrus.com, 
 Simon Trimmer <simont@opensource.cirrus.com>
In-Reply-To: <20240325144450.293630-1-rf@opensource.cirrus.com>
References: <20240325144450.293630-1-rf@opensource.cirrus.com>
Subject: Re: [PATCH] ASoC: cs-amp-lib: Check for no firmware controls when
 writing calibration
Message-Id: <171140567996.375229.415823964227571386.b4-ty@kernel.org>
Date: Mon, 25 Mar 2024 22:27:59 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Mon, 25 Mar 2024 14:44:50 +0000, Richard Fitzgerald wrote:
> When a wmfw file has not been loaded the firmware control descriptions
> necessary to write a stored calibration are not present. In this case
> print a more descriptive error message.
> 
> The message is logged at info level because it is not fatal, and does
> not necessarily imply that anything is broken.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs-amp-lib: Check for no firmware controls when writing calibration
      commit: e2d7ad717a6b0880843dbc60855a5b97ad0395f8

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