From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH v2 0/2] gcc-9 build fixes
Date: Thu, 29 Mar 2018 09:55:25 -0700 [thread overview]
Message-ID: <20180329165527.13109-1-stephen@networkplumber.org> (raw)
This fixes some of the obvious warnings found building DPDK
with gcc-8. There still are some deeper issues in the rte_hash_table
code; leave the fix for that up to the maintainer.
Stephen Hemminger (2):
rte_mbuf: fix strncpy warnings
rte_metrics: fix strncpy truncation warning
v2
fix issues with wrong length in mbuf pool_ops
don't need memset in metrics names
lib/librte_mbuf/rte_mbuf_pool_ops.c | 4 ++--
lib/librte_metrics/rte_metrics.c | 7 +++++--
2 files changed, 7 insertions(+), 4 deletions(-)
--
2.16.2
next reply other threads:[~2018-03-29 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 16:55 Stephen Hemminger [this message]
2018-03-29 16:55 ` [dpdk-dev] [PATCH v2 1/2] rte_mbuf: fix strncpy warnings Stephen Hemminger
2018-03-29 16:55 ` [dpdk-dev] [PATCH v2 2/2] rte_metrics: fix strncpy truncation warning Stephen Hemminger
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=20180329165527.13109-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--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).