[PATCH] ASoC: atmel: fix spelling mistake in Kconfig "programable" -> "programmable"
From: Colin Ian King colin.king@canonical.com
There are a couple of spelling mistakes in the Kconfig help text. Fix them.
Signed-off-by: Colin Ian King colin.king@canonical.com --- sound/soc/atmel/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/soc/atmel/Kconfig b/sound/soc/atmel/Kconfig index 142373ec411a..9fe9471f4514 100644 --- a/sound/soc/atmel/Kconfig +++ b/sound/soc/atmel/Kconfig @@ -143,7 +143,7 @@ config SND_MCHP_SOC_SPDIFTX - sama7g5
This S/PDIF TX driver is compliant with IEC-60958 standard and - includes programable User Data and Channel Status fields. + includes programmable User Data and Channel Status fields.
config SND_MCHP_SOC_SPDIFRX tristate "Microchip ASoC driver for boards using S/PDIF RX" @@ -157,5 +157,5 @@ config SND_MCHP_SOC_SPDIFRX - sama7g5
This S/PDIF RX driver is compliant with IEC-60958 standard and - includes programable User Data and Channel Status fields. + includes programmable User Data and Channel Status fields. endif
On 16.12.2020 13:26, Colin King wrote:
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
From: Colin Ian King colin.king@canonical.com
There are a couple of spelling mistakes in the Kconfig help text. Fix them.
Signed-off-by: Colin Ian King colin.king@canonical.com
Reviewed-by: Codrin Ciubotariu codrin.ciubotariu@microchip.com
Thanks!
On Wed, 16 Dec 2020 11:26:08 +0000, Colin King wrote:
There are a couple of spelling mistakes in the Kconfig help text. Fix them.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: atmel: fix spelling mistake in Kconfig "programable" -> "programmable" commit: 13733775326ea9eb81c6148ad60c43b8d231a343
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)
-
Codrin.Ciubotariu＠microchip.com -
Colin King -
Mark Brown