From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Daniel Mack <daniel@zonque.org>,
linux-wireless@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NFC: st95hf: fix spelling mistake: "receieve" -> "receive"
Date: Thu, 18 Apr 2019 16:12:01 +0530 [thread overview]
Message-ID: <15834163-7c70-3471-01bb-ad92fba3182e@codeaurora.org> (raw)
In-Reply-To: <20190418095756.9264-1-colin.king@canonical.com>
On 4/18/2019 3:27 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a dev_error message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> drivers/nfc/st95hf/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nfc/st95hf/core.c b/drivers/nfc/st95hf/core.c
> index a50a95cfcfd8..d72d48243141 100644
> --- a/drivers/nfc/st95hf/core.c
> +++ b/drivers/nfc/st95hf/core.c
> @@ -327,7 +327,7 @@ static int st95hf_echo_command(struct st95hf_context *st95context)
> &echo_response);
> if (result) {
> dev_err(&st95context->spicontext.spidev->dev,
> - "err: echo response receieve error = 0x%x\n", result);
> + "err: echo response receive error = 0x%x\n", result);
> return result;
> }
>
next prev parent reply other threads:[~2019-04-18 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 9:57 [PATCH] NFC: st95hf: fix spelling mistake: "receieve" -> "receive" Colin King
2019-04-18 10:42 ` Mukesh Ojha [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-29 11:03 [PATCH] NFC: st95hf: fix spelling mistake " Colin King
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=15834163-7c70-3471-01bb-ad92fba3182e@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=colin.king@canonical.com \
--cc=daniel@zonque.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@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