From: Oliver Graute <oliver.graute@gmail.com>
To: Yu Jiaoliang <yujiaoliang@vivo.com>
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Joel Selvaraj" <joelselvaraj.oss@gmail.com>,
"ye xingchen" <ye.xingchen@zte.com.cn>,
"Felix Kaechele" <felix@kaechele.ca>,
"Andreas Kemnade" <andreas@kemnade.info>,
"John Keeping" <jkeeping@inmusicbrands.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
patches@opensource.cirrus.com, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] input: Fix typos in comments across various files
Date: Thu, 26 Sep 2024 09:46:18 +0200 [thread overview]
Message-ID: <ZvURSswZLdAakNU6@graute-think> (raw)
In-Reply-To: <20240926031457.3479350-1-yujiaoliang@vivo.com>
On 26/09/24, Yu Jiaoliang wrote:
> This commit fixes several typographical errors in comments within
> the driver/input directory. No functional changes are made.
>
> Detected using codespell.
>
> Signed-off-by: Yu Jiaoliang <yujiaoliang@vivo.com>
Reviewed-by: Oliver Graute <oliver.graute@kococonnector.com>
next prev parent reply other threads:[~2024-09-26 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 3:14 [PATCH v1] input: Fix typos in comments across various files Yu Jiaoliang
2024-09-26 7:46 ` Oliver Graute [this message]
2024-09-30 14:58 ` Dmitry Torokhov
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=ZvURSswZLdAakNU6@graute-think \
--to=oliver.graute@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andreas@kemnade.info \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dmitry.torokhov@gmail.com \
--cc=felix@kaechele.ca \
--cc=jkeeping@inmusicbrands.com \
--cc=joelselvaraj.oss@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=opensource.kernel@vivo.com \
--cc=patches@opensource.cirrus.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ye.xingchen@zte.com.cn \
--cc=yujiaoliang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.