All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Rishi Gupta <gupt21@gmail.com>,
	sboyd@kernel.org,
	kernel-janitors <kernel-janitors@vger.kernel.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: Remove extraneous 'for' word in comments
Date: Sat, 17 Aug 2019 00:22:51 -0700	[thread overview]
Message-ID: <74b4a00b524cf8dd11631692dee65ccbba34b8cb.camel@perches.com> (raw)
In-Reply-To: <1566023759-7880-1-git-send-email-gupt21@gmail.com>

On Sat, 2019-08-17 at 12:05 +0530, Rishi Gupta wrote:
> An extra 'for' word is grammatically incorrect in the comment
> 'verifying ops for multi-parent clks'. This commit removes
> this extra for word.

A few other repeated word typos in comments are 
common in the kernel and most could be changed.

$ git grep -P '^\s*/?\*.*\bthe the\b' | wc -l
285
$ git grep -P '^\s*/?\*.*\bto to\b' | wc -l
62
$ git grep -P '^\s*/?\*.*\bfor for\b' | wc -l
31
$ git grep -P
'^\s*/?\*.*\bfrom from\b' | wc -l
22
$ git grep -P '^\s*/?\*.*\bare are\b'
| wc -l
16



WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Rishi Gupta <gupt21@gmail.com>,
	sboyd@kernel.org,
	kernel-janitors <kernel-janitors@vger.kernel.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: Remove extraneous 'for' word in comments
Date: Sat, 17 Aug 2019 07:22:51 +0000	[thread overview]
Message-ID: <74b4a00b524cf8dd11631692dee65ccbba34b8cb.camel@perches.com> (raw)
In-Reply-To: <1566023759-7880-1-git-send-email-gupt21@gmail.com>

On Sat, 2019-08-17 at 12:05 +0530, Rishi Gupta wrote:
> An extra 'for' word is grammatically incorrect in the comment
> 'verifying ops for multi-parent clks'. This commit removes
> this extra for word.

A few other repeated word typos in comments are 
common in the kernel and most could be changed.

$ git grep -P '^\s*/?\*.*\bthe the\b' | wc -l
285
$ git grep -P '^\s*/?\*.*\bto to\b' | wc -l
62
$ git grep -P '^\s*/?\*.*\bfor for\b' | wc -l
31
$ git grep -P
'^\s*/?\*.*\bfrom from\b' | wc -l
22
$ git grep -P '^\s*/?\*.*\bare are\b'
| wc -l
16

  reply	other threads:[~2019-08-17  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-17  6:35 [PATCH] clk: Remove extraneous 'for' word in comments Rishi Gupta
2019-08-17  7:22 ` Joe Perches [this message]
2019-08-17  7:22   ` Joe Perches
2019-08-17 14:57   ` Rishi Gupta
2019-08-17 14:58     ` Rishi Gupta
2019-08-18  1:13 ` Stephen Boyd

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=74b4a00b524cf8dd11631692dee65ccbba34b8cb.camel@perches.com \
    --to=joe@perches.com \
    --cc=gupt21@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    /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.