patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] acl: fix build with gcc 11
Date: Mon, 26 Apr 2021 16:30:40 +0100	[thread overview]
Message-ID: <d440f5ad-bd6c-8740-6c54-e9aaee04ed8b@redhat.com> (raw)
In-Reply-To: <DM4PR12MB5167BEC72FF3ED53851ADEC0DA429@DM4PR12MB5167.namprd12.prod.outlook.com>

On 26/04/2021 16:24, Ali Alnubani wrote:
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Konstantin Ananyev
>> Sent: Monday, April 26, 2021 4:35 PM
>> To: dev@dpdk.org
>> Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>; stable@dpdk.org
>> Subject: [dpdk-dev] [PATCH v2] acl: fix build with gcc 11
>>
> 
> Thanks Konstantin, I don't see the acl build failures with this patch.
> Tested with: meson --werror --buildtype=debugoptimized build && ninja -C build
> I see now new build errors in net/tap, test/test_cryptodev, and app/test-pmd. I'll open separate issues for these.
> 

Hi Ali,

There is already a Bz for test_cryptodev:
https://bugs.dpdk.org/show_bug.cgi?id=676

Kevin.

> Regards,
> Ali
> 


  reply	other threads:[~2021-04-26 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 13:54 [dpdk-stable] [PATCH] " Konstantin Ananyev
2021-04-26 13:35 ` [dpdk-stable] [PATCH v2] " Konstantin Ananyev
2021-04-26 15:24   ` [dpdk-stable] [dpdk-dev] " Ali Alnubani
2021-04-26 15:30     ` Kevin Traynor [this message]
2021-04-26 15:43       ` Ali Alnubani
2021-05-05 10:13   ` 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=d440f5ad-bd6c-8740-6c54-e9aaee04ed8b@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).