From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Purushothaman, Vijay A" <vijay.a.purushothaman@linux.intel.com>,
"Andy Whitcroft" <apw@canonical.com>,
"Joe Perches" <joe@perches.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: checkpatch spell checking (was: Re: [Intel-gfx] [PATCH] drm/i915: Reudce CHV DPLL min vco frequency to 4.8 GHz)
Date: Thu, 05 Mar 2015 09:43:34 +0200 [thread overview]
Message-ID: <87twxz3n4p.fsf@intel.com> (raw)
In-Reply-To: <20150304151002.GS11371@intel.com>
On Wed, 04 Mar 2015, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Mar 04, 2015 at 08:11:38PM +0530, Purushothaman, Vijay A wrote:
>> Minor nitpick: typo in patch title
>
> Dang. I already fixed a typo there before sending this out, but turns
> out I only managed to cchange it into a different typo :( Maybe I need
> to invest in a spell checker...
These days checkpatch.pl does some of this for you (see
scripts/spelling.txt). However your "reudce" isn't there, and, more
importantly, AFAICT checkpatch.pl does not look at the patch subject
anyway.
Joe, Andy, hint, hint. ;)
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next parent reply other threads:[~2015-03-05 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1424977312-24902-1-git-send-email-ville.syrjala@linux.intel.com>
[not found] ` <54F719A2.50405@linux.intel.com>
[not found] ` <20150304151002.GS11371@intel.com>
2015-03-05 7:43 ` Jani Nikula [this message]
2015-03-05 10:43 ` checkpatch spell checking (was: Re: [Intel-gfx] [PATCH] drm/i915: Reudce CHV DPLL min vco frequency to 4.8 GHz) Joe Perches
2015-03-05 16:57 ` [PATCH] checkpatch: Add spell checking of email subject line Joe Perches
2015-03-06 7:54 ` Jani Nikula
2015-03-06 8:40 ` [PATCH] checkpatch: spell check reudce Jani Nikula
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=87twxz3n4p.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=apw@canonical.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vijay.a.purushothaman@linux.intel.com \
--cc=ville.syrjala@linux.intel.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