From: Weihang Li <liweihang@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <linuxarm@huawei.com>,
Yixing Liu <liuyixing1@huawei.com>,
Weihang Li <liweihang@huawei.com>
Subject: [PATCH net-next 1/7] net: ena: fix inaccurate print type
Date: Wed, 31 Mar 2021 16:18:28 +0800 [thread overview]
Message-ID: <1617178714-14031-2-git-send-email-liweihang@huawei.com> (raw)
In-Reply-To: <1617178714-14031-1-git-send-email-liweihang@huawei.com>
From: Yixing Liu <liuyixing1@huawei.com>
Use "%u" to replace "hu%".
Signed-off-by: Yixing Liu <liuyixing1@huawei.com>
Signed-off-by: Weihang Li <liweihang@huawei.com>
---
drivers/net/ethernet/amazon/ena/ena_com.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/amazon/ena/ena_com.c b/drivers/net/ethernet/amazon/ena/ena_com.c
index 02087d4..764852e 100644
--- a/drivers/net/ethernet/amazon/ena/ena_com.c
+++ b/drivers/net/ethernet/amazon/ena/ena_com.c
@@ -863,7 +863,7 @@ static u32 ena_com_reg_bar_read32(struct ena_com_dev *ena_dev, u16 offset)
if (unlikely(i == timeout)) {
netdev_err(ena_dev->net_device,
- "Reading reg failed for timeout. expected: req id[%hu] offset[%hu] actual: req id[%hu] offset[%hu]\n",
+ "Reading reg failed for timeout. expected: req id[%u] offset[%u] actual: req id[%u] offset[%u]\n",
mmio_read->seq_num, offset, read_resp->req_id,
read_resp->reg_off);
ret = ENA_MMIO_READ_TIMEOUT;
@@ -2396,7 +2396,7 @@ int ena_com_fill_hash_function(struct ena_com_dev *ena_dev,
if (key) {
if (key_len != sizeof(hash_key->key)) {
netdev_err(ena_dev->net_device,
- "key len (%hu) doesn't equal the supported size (%zu)\n",
+ "key len (%u) doesn't equal the supported size (%zu)\n",
key_len, sizeof(hash_key->key));
return -EINVAL;
}
--
2.8.1
next prev parent reply other threads:[~2021-03-31 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 8:18 [PATCH net-next 0/7] net: fix some coding style issues Weihang Li
2021-03-31 8:18 ` Weihang Li [this message]
2021-03-31 8:18 ` [PATCH net-next 2/7] net: ena: remove extra words from comments Weihang Li
2021-03-31 8:18 ` [PATCH net-next 3/7] net: amd8111e: fix inappropriate spaces Weihang Li
2021-03-31 8:18 ` [PATCH net-next 4/7] net: amd: correct some format issues Weihang Li
2021-03-31 8:18 ` [PATCH net-next 5/7] net: ocelot: fix a trailling format issue with block comments Weihang Li
2021-03-31 8:18 ` [PATCH net-next 6/7] net: toshiba: fix the trailing format of some " Weihang Li
2021-03-31 8:18 ` [PATCH net-next 7/7] net: lpc_eth: fix format warnings of " Weihang Li
2021-03-31 21:50 ` [PATCH net-next 0/7] net: fix some coding style issues patchwork-bot+netdevbpf
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=1617178714-14031-2-git-send-email-liweihang@huawei.com \
--to=liweihang@huawei.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyixing1@huawei.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).