From: Kevin Traynor <ktraynor@redhat.com>
To: Luca Boccassi <bluca@debian.org>, stable@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: Re: [dpdk-stable] [PATCH 18.11 0/4] 18.11.9 build fixes
Date: Fri, 19 Jun 2020 10:38:10 +0100 [thread overview]
Message-ID: <833fb00e-ad53-bbaa-c265-0971cf833b98@redhat.com> (raw)
In-Reply-To: <5e1c3f3564a5097eea34feb2307d0f756077e20a.camel@debian.org>
On 17/06/2020 10:15, Luca Boccassi wrote:
> On Tue, 2020-06-16 at 14:51 +0100, Kevin Traynor wrote:
>> Various build fixes so that 18.11.9 will build with gcc 10
>>
>> Kevin Traynor (4):
>> kni: fix gcc 10 ethtool build error
>> kni: fix ethtool maybe-uninitialized warnings
>> crypto/octeontx: fix gcc 10 -fno-common build errors
>> app/testpmd: disable gcc 10 -fno-common build errors
>>
>> app/test-pmd/Makefile | 6 ++++++
>> app/test-pmd/meson.build | 5 +++++
>> drivers/common/cpt/cpt_pmd_logs.h | 2 +-
>> drivers/crypto/octeontx/otx_cryptodev.c | 2 ++
>> kernel/linux/kni/ethtool/igb/e1000_phy.c | 26 ++++++++++++++----------
>> 5 files changed, 29 insertions(+), 12 deletions(-)
>
> Series-Acked-By: Luca Boccassi <bluca@debian.org>
>
Applied, thanks
prev parent reply other threads:[~2020-06-19 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 13:51 Kevin Traynor
2020-06-16 13:51 ` [dpdk-stable] [PATCH 18.11 1/4] kni: fix gcc 10 ethtool build error Kevin Traynor
2020-06-16 13:51 ` [dpdk-stable] [PATCH 18.11 2/4] kni: fix ethtool maybe-uninitialized warnings Kevin Traynor
2020-06-16 13:51 ` [dpdk-stable] [PATCH 18.11 3/4] crypto/octeontx: fix gcc 10 -fno-common build errors Kevin Traynor
2020-06-16 13:51 ` [dpdk-stable] [PATCH 18.11 4/4] app/testpmd: disable " Kevin Traynor
2020-06-17 9:15 ` [dpdk-stable] [PATCH 18.11 0/4] 18.11.9 build fixes Luca Boccassi
2020-06-19 9:38 ` Kevin Traynor [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=833fb00e-ad53-bbaa-c265-0971cf833b98@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@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).