From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Colin King <colin.king@canonical.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, Minwoo Im <minwoo.im.dev@gmail.com>
Subject: Re: [PATCH][next] nvme-trace: fix spelling mistake "spcecific" -> "specific"
Date: Thu, 27 Jun 2019 05:10:39 +0900 [thread overview]
Message-ID: <20190626201039.GA4934@minwooim-desktop> (raw)
In-Reply-To: <20190626124323.5925-1-colin.king@canonical.com>
On 19-06-26 13:43:23, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are two spelling mistakes in trace_seq_printf messages, fix these.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/nvme/host/trace.c | 2 +-
> drivers/nvme/target/trace.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvme/host/trace.c b/drivers/nvme/host/trace.c
> index f01ad0fd60bb..6980ab827233 100644
> --- a/drivers/nvme/host/trace.c
> +++ b/drivers/nvme/host/trace.c
> @@ -178,7 +178,7 @@ static const char *nvme_trace_fabrics_common(struct trace_seq *p, u8 *spc)
> {
> const char *ret = trace_seq_buffer_ptr(p);
>
> - trace_seq_printf(p, "spcecific=%*ph", 24, spc);
> + trace_seq_printf(p, "specific=%*ph", 24, spc);
> trace_seq_putc(p, 0);
> return ret;
> }
> diff --git a/drivers/nvme/target/trace.c b/drivers/nvme/target/trace.c
> index cdcdd14c6408..6af11d493271 100644
> --- a/drivers/nvme/target/trace.c
> +++ b/drivers/nvme/target/trace.c
> @@ -146,7 +146,7 @@ static const char *nvmet_trace_fabrics_common(struct trace_seq *p, u8 *spc)
> {
> const char *ret = trace_seq_buffer_ptr(p);
>
> - trace_seq_printf(p, "spcecific=%*ph", 24, spc);
> + trace_seq_printf(p, "specific=%*ph", 24, spc);
> trace_seq_putc(p, 0);
> return ret;
> }
> --
> 2.20.1
>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
*facepalm*..
Thanks for fixing this, Colin!
Reviewed-by: Minwoo Im <minwoo.im.dev@gmail.com>
next prev parent reply other threads:[~2019-06-26 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 12:43 [PATCH][next] nvme-trace: fix spelling mistake "spcecific" -> "specific" Colin King
2019-06-26 20:10 ` Minwoo Im [this message]
2019-06-28 7:11 ` Christoph Hellwig
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=20190626201039.GA4934@minwooim-desktop \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=colin.king@canonical.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).