From: Conor Walsh <conor.walsh@intel.com>
To: bruce.richardson@intel.com, ajit.khaparde@broadcom.com,
somnath.kotur@broadcom.com, bluca@debian.org,
stuart.schacher@broadcom.com, venkatkumar.duvvuru@broadcom.com,
michael.wildt@broadcom.com
Cc: dev@dpdk.org, linglix.chen@intel.com, thomas@monjalon.net,
Conor Walsh <conor.walsh@intel.com>
Subject: [dpdk-dev] [PATCH v2 2/2] net/bnxt: fix format characters for unsigned values
Date: Wed, 18 Nov 2020 18:11:03 +0000 [thread overview]
Message-ID: <20201118181103.3865787-3-conor.walsh@intel.com> (raw)
In-Reply-To: <20201118181103.3865787-1-conor.walsh@intel.com>
&device requires the %u format specifer not the %d specifier, as
&device is unsigned.
Fixes: a46bbb57605b ("net/bnxt: update multi device design")
Cc: michael.wildt@broadcom.com
Signed-off-by: Conor Walsh <conor.walsh@intel.com>
---
drivers/net/bnxt/tf_core/tf_core.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/bnxt/tf_core/tf_core.c b/drivers/net/bnxt/tf_core/tf_core.c
index 0f49a00256..24d49096a7 100644
--- a/drivers/net/bnxt/tf_core/tf_core.c
+++ b/drivers/net/bnxt/tf_core/tf_core.c
@@ -44,7 +44,7 @@ tf_open_session(struct tf *tfp,
/* Verify control channel and build the beginning of session_id */
rc = sscanf(parms->ctrl_chan_name,
- "%x:%x:%x.%d",
+ "%x:%x:%x.%u",
&domain,
&bus,
&slot,
@@ -57,7 +57,7 @@ tf_open_session(struct tf *tfp,
/* Check parsing of bus/slot/device */
rc = sscanf(parms->ctrl_chan_name,
- "%x:%x.%d",
+ "%x:%x.%u",
&bus,
&slot,
&device);
@@ -102,7 +102,7 @@ tf_attach_session(struct tf *tfp,
/* Verify control channel */
rc = sscanf(parms->ctrl_chan_name,
- "%x:%x:%x.%d",
+ "%x:%x:%x.%u",
&domain,
&bus,
&slot,
@@ -115,7 +115,7 @@ tf_attach_session(struct tf *tfp,
/* Verify 'attach' channel */
rc = sscanf(parms->attach_chan_name,
- "%x:%x:%x.%d",
+ "%x:%x:%x.%u",
&domain,
&bus,
&slot,
--
2.25.1
next prev parent reply other threads:[~2020-11-18 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 11:35 [dpdk-dev] [PATCH v1] build: add Wformat to fix gcc compile error Conor Walsh
2020-11-12 18:47 ` Thomas Monjalon
2020-11-13 13:54 ` Walsh, Conor
2020-11-13 3:39 ` Chen, LingliX
2020-11-18 18:11 ` [dpdk-dev] [PATCH v2 0/2] build: add Wformat to fix gcc compile warnings and format fixes Conor Walsh
2020-11-18 18:11 ` [dpdk-dev] [PATCH v2 1/2] build: fix gcc compile warnings by adding wformat Conor Walsh
2020-11-18 18:11 ` Conor Walsh [this message]
2020-11-18 18:37 ` [dpdk-dev] [PATCH v2 0/2] build: add Wformat to fix gcc compile warnings and format fixes Luca Boccassi
2020-11-19 10:24 ` Walsh, Conor
2020-11-19 10:16 ` [dpdk-dev] [PATCH v3 " Conor Walsh
2020-11-19 10:16 ` [dpdk-dev] [PATCH v3 1/2] build: fix gcc compile warnings by adding wformat Conor Walsh
2020-11-20 7:23 ` Chen, LingliX
2020-11-19 10:17 ` [dpdk-dev] [PATCH v3 2/2] net/bnxt: fix format characters for unsigned values Conor Walsh
2020-11-19 23:12 ` Ajit Khaparde
2020-11-22 20:07 ` [dpdk-dev] [dpdk-stable] [PATCH v3 0/2] build: add Wformat to fix gcc compile warnings and format fixes Thomas Monjalon
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=20201118181103.3865787-3-conor.walsh@intel.com \
--to=conor.walsh@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=linglix.chen@intel.com \
--cc=michael.wildt@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stuart.schacher@broadcom.com \
--cc=thomas@monjalon.net \
--cc=venkatkumar.duvvuru@broadcom.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).