ASoC: q6asm: fix 'physical' typos
Subsystems (3)
PATCH 1/1 ASoC: q6asm: fix 'physical' typos
From: Bjorn Helgaas <[email protected]>
Fix misspellings of "physical".
--- sound/soc/qcom/qdsp6/q6asm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/qcom/qdsp6/q6asm.c +1 -1
@@ -491,7 +491,7 @@ static int __q6asm_memory_map_regions(struct audio_client *ac, int dir,* * @dir: direction of audio stream * @ac: audio client instanace -* @phys: physcial address that needs mapping. +* @phys: physical address that needs mapping. * @period_sz: audio period size * @periods: number of periods *
Signature · 1 line
2.25.1
Quoted 5 lines · Bjorn Helgaas
From: Bjorn Helgaas <[email protected]>
Fix misspellings of "physical".
Signed-off-by Bjorn Helgaas <[email protected]>
Quoted 18 lines
--- sound/soc/qcom/qdsp6/q6asm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)sound/soc/qcom/qdsp6/q6asm.c +1
-1@@ -491,7 +491,7 @@ static int __q6asm_memory_map_regions(struct audio_client *ac, int dir,* * @dir: direction of audio stream * @ac: audio client instanace -* @phys: physcial address that needs mapping. +* @phys: physical address that needs mapping. * @period_sz: audio period size * @periods: number of periods *
Mark Brown
maintainerQuoted 1 line · Bjorn Helgaas
Fix misspellings of "physical".
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: q6asm: fix 'physical' typos
commit: 9fd5599a9b2618b315983d8a097e6dead640f55c
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