From: Joe Perches <joe@perches.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Kees Cook <keescook@chromium.org>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Purushothaman, Vijay A" <vijay.a.purushothaman@linux.intel.com>,
"Andy Whitcroft" <apw@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: 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 02:43:22 -0800 [thread overview]
Message-ID: <1425552202.2712.30.camel@perches.com> (raw)
In-Reply-To: <87twxz3n4p.fsf@intel.com>
On Thu, 2015-03-05 at 09:43 +0200, Jani Nikula wrote:
> 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. ;)
Patches happily accepted, (hint back..:)
(adding Kees Cook too)
next prev parent reply other threads:[~2015-03-05 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 19:01 [PATCH] drm/i915: Reudce CHV DPLL min vco frequency to 4.8 GHz ville.syrjala
2015-03-01 3:52 ` shuang.he
2015-03-04 14:41 ` Purushothaman, Vijay A
2015-03-04 15:10 ` Ville Syrjälä
2015-03-04 15:15 ` Daniel Vetter
2015-03-05 7:43 ` checkpatch spell checking (was: Re: [PATCH] drm/i915: Reudce CHV DPLL min vco frequency to 4.8 GHz) Jani Nikula
2015-03-05 7:43 ` checkpatch spell checking (was: Re: [Intel-gfx] " Jani Nikula
2015-03-05 10:43 ` Joe Perches [this message]
2015-03-05 16:57 ` [PATCH] checkpatch: Add spell checking of email subject line Joe Perches
2015-03-05 16:57 ` Joe Perches
2015-03-06 7:54 ` Jani Nikula
2015-03-06 7:54 ` Jani Nikula
2015-03-06 8:40 ` [PATCH] checkpatch: spell check reudce Jani Nikula
2015-03-06 8:40 ` Jani Nikula
2015-03-06 11:41 ` shuang.he
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=1425552202.2712.30.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=keescook@chromium.org \
--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 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.