From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH iproute2 0/5] fix warnings from gcc-10
Date: Sun, 29 Nov 2020 16:17:25 -0800 [thread overview]
Message-ID: <20201129161725.0e9277d4@hermes.local> (raw)
In-Reply-To: <20201129175437.15346-1-stephen@networkplumber.org>
On Sun, 29 Nov 2020 09:54:32 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:
> Just switched over to Gcc-10 which complains about a number
> of small issues in iproute2.
>
> Stephen Hemminger (5):
> devlink: fix unitialized warning
> bridge: fix string length warning
> tc: fix compiler warnings in ip6 pedit
> misc: fix compiler warning in ifstat and nstat
> f_u32: fix compiler gcc-10 compiler warning
>
> devlink/devlink.c | 2 +-
> ip/iplink_bridge.c | 2 +-
> misc/ifstat.c | 2 +-
> misc/nstat.c | 3 +--
> tc/f_u32.c | 2 +-
> tc/p_ip6.c | 2 +-
> 6 files changed, 6 insertions(+), 7 deletions(-)
>
Ignore this meant to go to netdev, and send-email became automatic to dev@dpdk.org
prev parent reply other threads:[~2020-11-30 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 17:54 Stephen Hemminger
2020-11-29 17:54 ` [dpdk-dev] [PATCH 1/5] devlink: fix unitialized warning Stephen Hemminger
2020-11-29 17:54 ` [dpdk-dev] [PATCH 2/5] bridge: fix string length warning Stephen Hemminger
2020-11-29 17:54 ` [dpdk-dev] [PATCH 3/5] tc: fix compiler warnings in ip6 pedit Stephen Hemminger
2020-11-29 17:54 ` [dpdk-dev] [PATCH 4/5] misc: fix compiler warning in ifstat and nstat Stephen Hemminger
2020-11-29 17:54 ` [dpdk-dev] [PATCH 5/5] f_u32: fix compiler gcc-10 compiler warning Stephen Hemminger
2020-11-30 0:17 ` Stephen Hemminger [this message]
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=20201129161725.0e9277d4@hermes.local \
--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).