From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, Nithin Dabilpuram <ndabilpuram@marvell.com>,
"Kiran Kumar K" <kirankumark@marvell.com>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [PATCH] net/octeontx2: fix compilation with x86_x32
Date: Thu, 31 Oct 2019 00:01:42 +0530 [thread overview]
Message-ID: <20191030183143.905-1-pbhagavatula@marvell.com> (raw)
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
x86_x32 compilation failing due to incorrect format specifiers in logs.
Fixes: a78b9246723b ("net/octeontx2: add remaining PTP operations")
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
drivers/net/octeontx2/otx2_ptp.c | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/net/octeontx2/otx2_ptp.c b/drivers/net/octeontx2/otx2_ptp.c
index fd13c2678..7efdbba1f 100644
--- a/drivers/net/octeontx2/otx2_ptp.c
+++ b/drivers/net/octeontx2/otx2_ptp.c
@@ -259,9 +259,9 @@ otx2_nix_timesync_read_rx_timestamp(struct rte_eth_dev *eth_dev,
*timestamp = rte_ns_to_timespec(ns);
tstamp->rx_ready = 0;
- otx2_nix_dbg("rx timestamp: %llu sec: %lu nsec %lu",
- (unsigned long long)tstamp->rx_tstamp, timestamp->tv_sec,
- timestamp->tv_nsec);
+ otx2_nix_dbg("rx timestamp: %"PRIu64" sec: %"PRIu64" nsec %"PRIu64"",
+ (uint64_t)tstamp->rx_tstamp, (uint64_t)timestamp->tv_sec,
+ (uint64_t)timestamp->tv_nsec);
return 0;
}
@@ -280,9 +280,9 @@ otx2_nix_timesync_read_tx_timestamp(struct rte_eth_dev *eth_dev,
ns = rte_timecounter_update(&dev->tx_tstamp_tc, *tstamp->tx_tstamp);
*timestamp = rte_ns_to_timespec(ns);
- otx2_nix_dbg("tx timestamp: %llu sec: %lu nsec %lu",
- *(unsigned long long *)tstamp->tx_tstamp,
- timestamp->tv_sec, timestamp->tv_nsec);
+ otx2_nix_dbg("tx timestamp: %"PRIu64" sec: %"PRIu64" nsec %"PRIu64"",
+ *tstamp->tx_tstamp, (uint64_t)timestamp->tv_sec,
+ (uint64_t)timestamp->tv_nsec);
*tstamp->tx_tstamp = 0;
rte_wmb();
@@ -358,7 +358,8 @@ otx2_nix_timesync_read_time(struct rte_eth_dev *eth_dev, struct timespec *ts)
ns = rte_timecounter_update(&dev->systime_tc, rsp->clk);
*ts = rte_ns_to_timespec(ns);
- otx2_nix_dbg("PTP time read: %ld.%09ld", ts->tv_sec, ts->tv_nsec);
+ otx2_nix_dbg("PTP time read: %"PRIu64" .%09"PRIu64"",
+ (uint64_t)ts->tv_sec, (uint64_t)ts->tv_nsec);
return 0;
}
--
2.20.1
next reply other threads:[~2019-10-30 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 18:31 pbhagavatula [this message]
2019-11-06 0:43 ` Gavin Hu (Arm Technology China)
2019-11-06 6:41 ` Jerin Jacob
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=20191030183143.905-1-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.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).