The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dejin Zheng <zhengdejin5@gmail.com>,
	aisheng.dong@nxp.com, festevam@gmail.com, shawnguo@kernel.org,
	stefan@agner.ch, kernel@pengutronix.de, linus.walleij@linaro.org,
	s.hauer@pengutronix.de, geert+renesas@glider.be,
	thierry.reding@gmail.com, jonathanh@nvidia.com,
	jun.nie@linaro.org, stephan@gerhold.net,
	linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v1] pinctrl: fix several typos
Date: Mon, 20 Apr 2020 09:41:09 -0700	[thread overview]
Message-ID: <f54d6f0a6c31ab3911c2b35caef49df340ab1196.camel@perches.com> (raw)
In-Reply-To: <20200419164956.3484-1-zhengdejin5@gmail.com>

On Mon, 2020-04-20 at 00:49 +0800, Dejin Zheng wrote:
> use codespell to fix lots of typos over frontends.
[]
> diff --git a/drivers/pinctrl/nomadik/pinctrl-nomadik-db8500.c b/drivers/pinctrl/nomadik/pinctrl-nomadik-db8500.c
[]
> @@ -418,7 +418,7 @@ static const unsigned lcdvsi1_a_1_pins[] = { DB8500_PIN_E2 };
>  static const unsigned lcd_d0_d7_a_1_pins[] = {
>  	DB8500_PIN_G5, DB8500_PIN_G4, DB8500_PIN_H4, DB8500_PIN_H3,
>  	DB8500_PIN_J3, DB8500_PIN_H2, DB8500_PIN_J2, DB8500_PIN_H1 };
> -/* D8 thru D11 often used as TVOUT lines */
> +/* D8 through D11 often used as TVOUT lines */

thru is _really_ common and a generally accepted informal
for through so I suggest this not be changed.

https://www.dictionary.com/browse/thru
preposition, adverb, adjective
an informal, simplified spelling of through.

https://www.merriam-webster.com/dictionary/thru
While never extremely common, tho and thru have a long history of
occasional use as spelling variants of though and through.

Their greatest popularity occurred in the late 19th and early 20th 
centuries, when their adoption was advocated by spelling reformers. 
Their current use occurs chiefly in informal writing (as in personal 
letters) and in some technical journals.


  parent reply	other threads:[~2020-04-20 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 16:49 [PATCH v1] pinctrl: fix several typos Dejin Zheng
2020-04-19 17:10 ` Uwe Kleine-König
2020-04-19 17:54 ` Geert Uytterhoeven
2020-04-20 16:41 ` Joe Perches [this message]
2020-04-21 14:34   ` Dejin Zheng

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=f54d6f0a6c31ab3911c2b35caef49df340ab1196.camel@perches.com \
    --to=joe@perches.com \
    --cc=aisheng.dong@nxp.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=jonathanh@nvidia.com \
    --cc=jun.nie@linaro.org \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=stephan@gerhold.net \
    --cc=thierry.reding@gmail.com \
    --cc=zhengdejin5@gmail.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