From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Colin King <colin.king@canonical.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARC: fix spelling mistake "entires" -> "entries"
Date: Fri, 14 Sep 2018 17:33:38 +0000 [thread overview]
Message-ID: <C2D7FE5348E1B147BCA15975FBA23075012B095203@us01wembx1.internal.synopsys.com> (raw)
In-Reply-To: 20180914112727.4276-1-colin.king@canonical.com
On 09/14/2018 04:27 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in Kconfig
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied !
Thx,
-Vineet
prev parent reply other threads:[~2018-09-14 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 11:27 [PATCH] ARC: fix spelling mistake "entires" -> "entries" Colin King
2018-09-14 17:33 ` Vineet Gupta [this message]
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=C2D7FE5348E1B147BCA15975FBA23075012B095203@us01wembx1.internal.synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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).