From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] fix build with GCC 10
Date: Wed, 20 May 2020 16:52:55 +0200 [thread overview]
Message-ID: <CAJFAV8zGRR3OdSFQdTPDouwesrpJFdh3w2=u4Px=scEFOc_m0A@mail.gmail.com> (raw)
In-Reply-To: <20200520135830.1178242-1-thomas@monjalon.net>
On Wed, May 20, 2020 at 3:58 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> These are supposed to be the last patches to support GCC 10.
>
> Thomas Monjalon (4):
> net/mvpp2: fix build with gcc 10
> examples/vm_power: fix build with -fno-common
> examples/vm_power: drop Unix path limit redefinition
> devtools: allow warnings in ABI reference build
>
> devtools/test-build.sh | 6 ++----
> devtools/test-meson-builds.sh | 3 +--
> drivers/net/mvpp2/mrvl_flow.c | 4 ++--
> examples/vm_power_manager/channel_manager.c | 3 ++-
> examples/vm_power_manager/channel_manager.h | 9 ++-------
> examples/vm_power_manager/power_manager.c | 1 -
> 6 files changed, 9 insertions(+), 17 deletions(-)
For the series,
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2020-05-20 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 13:58 [dpdk-dev] [PATCH 0/4] fix build with GCC 10 Thomas Monjalon
2020-05-20 13:58 ` [dpdk-dev] [PATCH 1/4] net/mvpp2: fix build with gcc 10 Thomas Monjalon
2020-05-20 14:05 ` [dpdk-dev] [EXT] " Liron Himi
2020-05-20 13:58 ` [dpdk-dev] [PATCH 2/4] examples/vm_power: fix build with -fno-common Thomas Monjalon
2020-05-20 13:58 ` [dpdk-dev] [PATCH 3/4] examples/vm_power: drop Unix path limit redefinition Thomas Monjalon
2020-05-20 13:58 ` [dpdk-dev] [PATCH 4/4] devtools: allow warnings in ABI reference build Thomas Monjalon
2020-05-20 14:52 ` David Marchand [this message]
2020-05-20 16:45 ` [dpdk-dev] [PATCH 0/4] fix build with GCC 10 Kevin Traynor
2020-05-21 13:39 ` 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='CAJFAV8zGRR3OdSFQdTPDouwesrpJFdh3w2=u4Px=scEFOc_m0A@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.