From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: madalin.bucur@nxp.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsl/fman: fix spelling mistake in variable name en_tsu_err_exeption
Date: Mon, 20 Feb 2017 10:28:54 -0500 (EST) [thread overview]
Message-ID: <20170220.102854.363621552857347906.davem@davemloft.net> (raw)
In-Reply-To: <20170218234146.20041-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Sat, 18 Feb 2017 23:41:46 +0000
> From: Colin Ian King <colin.king@canonical.com>
>
> trivial fix to spelling mistake, en_tsu_err_exeption should
> be en_tsu_err_exception
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied.
prev parent reply other threads:[~2017-02-20 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 23:41 [PATCH] fsl/fman: fix spelling mistake in variable name en_tsu_err_exeption Colin King
2017-02-20 15:28 ` David Miller [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=20170220.102854.363621552857347906.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.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 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).