From: patchwork-bot+bluetooth@kernel.org
To: Yan Zhen <yanzhen@vivo.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
sean.wang@mediatek.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] bluetooth: Fix typos in the comments
Date: Tue, 01 Oct 2024 15:20:34 +0000 [thread overview]
Message-ID: <172779603451.424883.16063021833718946577.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240929085727.523732-1-yanzhen@vivo.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 29 Sep 2024 16:57:27 +0800 you wrote:
> Correctly spelled comments make it easier for the reader to understand
> the code.
>
> Fix typos:
> 'fragement' ==> 'fragment',
> 'genration' ==> 'generation',
> 'funciton' ==> 'function',
> 'Explitly' ==> 'Explicitly',
> 'explaination' ==> 'explanation',
> 'Tranlate' ==> 'Translate',
> 'immediatelly' ==> 'immediately',
> 'isntance' ==> 'instance',
> 'transmittion' ==> 'transmission',
> 'recevie' ==> 'receive',
> 'outselves' ==> 'ourselves',
> 'conrol' ==> 'control'.
>
> [...]
Here is the summary with links:
- [v1] bluetooth: Fix typos in the comments
https://git.kernel.org/bluetooth/bluetooth-next/c/89f69afc2c4e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-01 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 8:57 [PATCH v1] bluetooth: Fix typos in the comments Yan Zhen
2024-10-01 7:51 ` AngeloGioacchino Del Regno
2024-10-01 15:20 ` patchwork-bot+bluetooth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=172779603451.424883.16063021833718946577.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=opensource.kernel@vivo.com \
--cc=sean.wang@mediatek.com \
--cc=yanzhen@vivo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox