[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172773251765.2210210.17538340798969212217.b4-ty@kernel.org>
Date: Mon, 30 Sep 2024 22:41:57 +0100
From: Mark Brown <broonie@...nel.org>
To: f.fangjian@...wei.com, linus.walleij@...aro.org, heiko@...ech.de,
andi.shyti@...nel.org, krzk@...nel.org, orsonzhai@...il.com,
baolin.wang@...ux.alibaba.com, ldewangan@...dia.com,
thierry.reding@...il.com, jonathanh@...dia.com, Yan Zhen <yanzhen@...o.com>
Cc: alim.akhtar@...sung.com, zhang.lyra@...il.com,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-tegra@...r.kernel.org,
opensourec.kernel@...o.com
Subject: Re: [PATCH v1] spi: fix typo in the comment
On Sat, 14 Sep 2024 17:52:13 +0800, Yan Zhen wrote:
> Correctly spelled comments make it easier for the reader to understand
> the code.
>
> Replace 'progrom' with 'program' in the comment &
> replace 'Recevie' with 'Receive' in the comment &
> replace 'receieved' with 'received' in the comment &
> replace 'ajacent' with 'adjacent' in the comment &
> replace 'trasaction' with 'transaction' in the comment &
> replace 'pecularity' with 'peculiarity' in the comment &
> replace 'resiter' with 'register' in the comment &
> replace 'tansmition' with 'transmission' in the comment &
> replace 'Deufult' with 'Default' in the comment &
> replace 'tansfer' with 'transfer' in the comment &
> replace 'settign' with 'setting' in the comment.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: fix typo in the comment
commit: 89980d3a34655d99c599f6acf877fd48775a29ad
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
Powered by blists - more mailing lists