[Sound-open-firmware] [PATCH] ASoC: SOF: Fix spelling mistake in Kconfig "ond" -> "and"
From: Colin Ian King colin.king@canonical.com
There is a spelling mistake in the Kconfig help text. Fix it.
Signed-off-by: Colin Ian King colin.king@canonical.com --- sound/soc/sof/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/sof/Kconfig b/sound/soc/sof/Kconfig index 031dad5fc4c7..3e8b6c035ce3 100644 --- a/sound/soc/sof/Kconfig +++ b/sound/soc/sof/Kconfig @@ -122,7 +122,7 @@ config SND_SOC_SOF_DEBUG_XRUN_STOP bool "SOF stop on XRUN" help This option forces PCMs to stop on any XRUN event. This is useful to - preserve any trace data ond pipeline status prior to the XRUN. + preserve any trace data and pipeline status prior to the XRUN. Say Y if you are debugging SOF FW pipeline XRUNs. If unsure select "N".
Hi,
thanks Colin.
On Wed, 16 Dec 2020, Colin King wrote:
From: Colin Ian King colin.king@canonical.com
There is a spelling mistake in the Kconfig help text. Fix it.
Signed-off-by: Colin Ian King colin.king@canonical.com
Acked-by: Kai Vehmanen kai.vehmanen@linux.intel.com
Br, kai
On Wed, 16 Dec 2020 12:59:13 +0000, Colin King wrote:
There is a spelling mistake in the Kconfig help text. Fix it.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: Fix spelling mistake in Kconfig "ond" -> "and" commit: e49037ad12e47cd34239b99b010c5438844923af
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
participants (3)
-
Colin King -
Kai Vehmanen -
Mark Brown