sound/soc/tegra: Fix spelling error 'recieved' -> 'received'
Subsystems (3)
PATCH 1/1 sound/soc/tegra: Fix spelling error 'recieved' -> 'received'
Fix typo in comment where 'recieved' should be 'received'.
--- sound/soc/tegra/tegra20_spdif.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/tegra/tegra20_spdif.h +1 -1
@@ -171,7 +171,7 @@/* * RX channel block data receive status: -* 0=entire block not recieved yet. +* 0=entire block not received yet. * 1=received entire block of channel status, */ #define TEGRA20_SPDIF_STATUS_IS_C (1 << 21)
Signature · 1 line
2.40.1
Mark Brown
maintainerQuoted 1 line · Qinghua Zhao
Fix typo in comment where 'recieved' should be 'received'.
Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone.
Mark Brown
maintainerQuoted 1 line · Qinghua Zhao
sound/soc/tegra: Fix spelling error 'recieved' -> 'received'
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.1
Thanks!
[1/1] sound/soc/tegra: Fix spelling error 'recieved' -> 'received'
https://git.kernel.org/broonie/sound/c/833011cbe663
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