From: devyn.johnson@banduracyber.com
To: dev@dpdk.org
Cc: Devyn Collier Johnson <Devyn.Johnson@BanduraCyber.com>
Subject: [dpdk-dev] [PATCH] Fixed one missed request for the mailing-list patch-checker
Date: Tue, 5 Nov 2019 12:45:49 -0600 [thread overview]
Message-ID: <20191105184549.5122-1-Devyn.Johnson@BanduraCyber.com> (raw)
In-Reply-To: <20191105181640.3714-1-Devyn.Johnson@BanduraCyber.com>
From: Devyn Collier Johnson <Devyn.Johnson@BanduraCyber.com>
Signed-off-by: Devyn Collier Johnson <Devyn.Johnson@BanduraCyber.com>
---
lib/librte_mbuf/rte_mbuf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_mbuf/rte_mbuf.c b/lib/librte_mbuf/rte_mbuf.c
index f3fe16eb0..305084531 100644
--- a/lib/librte_mbuf/rte_mbuf.c
+++ b/lib/librte_mbuf/rte_mbuf.c
@@ -474,7 +474,7 @@ rte_pktmbuf_dump(FILE *f, const struct rte_mbuf *m, unsigned dump_len)
__rte_mbuf_sanity_check(m, 1);
fprintf(f, "dump mbuf at %p, iova=%"PRIx64", buf_len=%u\n",
- (const void *)m, (uint64_t)m->buf_iova, (unsigned)m->buf_len);
+ (const void *)m, (uint64_t)m->buf_iova, (unsigned int)m->buf_len);
fprintf(f, " pkt_len=%"PRIu32", ol_flags=%"PRIx64", nb_segs=%u, "
"in_port=%u\n", m->pkt_len, m->ol_flags,
(unsigned)m->nb_segs, (unsigned)m->port);
--
2.17.1
next prev parent reply other threads:[~2019-11-05 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 18:16 [dpdk-dev] [PATCH] Working Towards Making DPDK Compile with Additional Warning Flags devyn.johnson
2019-11-05 18:36 ` [dpdk-dev] [PATCH] Applied tweaks requested by the mailing-list patch-checker devyn.johnson
2019-11-05 18:45 ` devyn.johnson [this message]
2019-11-05 19:35 ` [dpdk-dev] [PATCH] Working Towards Making DPDK Compile with Additional Warning Flags David Marchand
2019-11-05 21:04 ` Devyn Johnson
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=20191105184549.5122-1-Devyn.Johnson@BanduraCyber.com \
--to=devyn.johnson@banduracyber.com \
--cc=dev@dpdk.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).