ASoC: atmel: fix spelling mistake in Kconfig "programable" -> "programmable"
Subsystems (5)
PATCH 1/1 ASoC: atmel: fix spelling mistake in Kconfig "programable" -> "programmable"
From: Colin Ian King <[email protected]>
There are a couple of spelling mistakes in the Kconfig help text. Fix them.
--- sound/soc/atmel/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
sound/soc/atmel/Kconfig +2 -2
@@ -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
Signature · 1 line
2.29.2
T24gMTYuMTIuMjAyMCAxMzoyNiwgQ29saW4gS2luZyB3cm90ZToNCj4gRVhURVJOQUwgRU1BSUw6 IERvIG5vdCBjbGljayBsaW5rcyBvciBvcGVuIGF0dGFjaG1lbnRzIHVubGVzcyB5b3Uga25vdyB0 aGUgY29udGVudCBpcyBzYWZlDQo+IA0KPiBGcm9tOiBDb2xpbiBJYW4gS2luZyA8Y29saW4ua2lu Z0BjYW5vbmljYWwuY29tPg0KPiANCj4gVGhlcmUgYXJlIGEgY291cGxlIG9mIHNwZWxsaW5nIG1p c3Rha2VzIGluIHRoZSBLY29uZmlnIGhlbHAgdGV4dC4gRml4IHRoZW0uDQo+IA0KPiBTaWduZWQt b2ZmLWJ5OiBDb2xpbiBJYW4gS2luZyA8Y29saW4ua2luZ0BjYW5vbmljYWwuY29tPg0KDQpSZXZp ZXdlZC1ieTogQ29kcmluIENpdWJvdGFyaXUgPGNvZHJpbi5jaXVib3Rhcml1QG1pY3JvY2hpcC5j b20+DQoNClRoYW5rcyENCg=
Mark Brown
maintainerQuoted 1 line · Colin King
There are a couple of spelling mistakes in the
Kconfighelp 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