From: Hu Haowen <xianfengting221@163.com>
To: saeedm@mellanox.com, leon@kernel.org, davem@davemloft.net
Cc: moshe@mellanox.com, lsahlber@redhat.com, kw@linux.com,
wqu@suse.com, xiubli@redhat.com, xianfengting221@163.com,
chris@chris-wilson.co.uk, stfrench@microsoft.com,
airlied@redhat.com, yamada.masahiro@socionext.com, cai@lca.pw,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] net/mlx5: add the missing space character
Date: Fri, 3 Apr 2020 12:26:59 +0800 [thread overview]
Message-ID: <20200403042659.9167-1-xianfengting221@163.com> (raw)
Commit 91b56d8462a9 ("net/mlx5: improve some comments") did not add
that missing space character and this commit is used to fix it up.
Fixes: 91b56d8462a9 ("net/mlx5: improve some comments")
Signed-off-by: Hu Haowen <xianfengting221@163.com>
---
drivers/net/ethernet/mellanox/mlx5/core/diag/fw_tracer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/diag/fw_tracer.c b/drivers/net/ethernet/mellanox/mlx5/core/diag/fw_tracer.c
index c9c9b479bda5..31bddb48e5c3 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/diag/fw_tracer.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/diag/fw_tracer.c
@@ -676,7 +676,7 @@ static void mlx5_fw_tracer_handle_traces(struct work_struct *work)
block_count = tracer->buff.size / TRACER_BLOCK_SIZE_BYTE;
start_offset = tracer->buff.consumer_index * TRACER_BLOCK_SIZE_BYTE;
- /* Copy the block to local buffer to avoid HW override while being processed*/
+ /* Copy the block to local buffer to avoid HW override while being processed */
memcpy(tmp_trace_block, tracer->buff.log_buf + start_offset,
TRACER_BLOCK_SIZE_BYTE);
--
2.20.1
next reply other threads:[~2020-04-03 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 4:26 Hu Haowen [this message]
2020-04-08 19:42 ` [PATCH v2] net/mlx5: add the missing space character Saeed Mahameed
2020-04-16 14:44 ` Hu Haowen
2020-04-17 3:44 ` Saeed Mahameed
2020-04-17 4:34 ` Hu Haowen
2020-04-17 22:40 ` Saeed Mahameed
2020-04-18 12:54 ` Hu Haowen
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=20200403042659.9167-1-xianfengting221@163.com \
--to=xianfengting221@163.com \
--cc=airlied@redhat.com \
--cc=cai@lca.pw \
--cc=chris@chris-wilson.co.uk \
--cc=davem@davemloft.net \
--cc=kw@linux.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=stfrench@microsoft.com \
--cc=wqu@suse.com \
--cc=xiubli@redhat.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).