From: Joe Perches <joe@perches.com>
To: Colin King <colin.king@canonical.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-msm: fix spelling mistake: "Perpheral" -> "Peripheral"
Date: Thu, 23 Jun 2016 04:39:22 -0700 [thread overview]
Message-ID: <1466681962.1847.2.camel@perches.com> (raw)
In-Reply-To: <1466675526-3176-1-git-send-email-colin.king@canonical.com>
On Thu, 2016-06-23 at 10:52 +0100, Colin King wrote:
> trivial fix to spelling mistake in dev_err message
Hello Colin.
You are submitting a lot of these recently.
Are you using a tool to find these?
If you are, maybe publish it to the janitorial
and newbies list so others can do the work.
next prev parent reply other threads:[~2016-06-23 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 9:52 [PATCH] mmc: sdhci-msm: fix spelling mistake: "Perpheral" -> "Peripheral" Colin King
2016-06-23 10:38 ` Adrian Hunter
2016-06-23 11:39 ` Joe Perches [this message]
2016-06-23 11:59 ` Colin Ian King
2016-06-27 9:21 ` Ulf Hansson
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=1466681962.1847.2.camel@perches.com \
--to=joe@perches.com \
--cc=adrian.hunter@intel.com \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).