patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Liang Ma <liangma@liangbit.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] acl: fix build with GCC 6.3
Date: Fri, 21 May 2021 15:55:58 +0100	[thread overview]
Message-ID: <YKfJ/olz/QgDR8A3@C02F33EJML85> (raw)
In-Reply-To: <20210521144207.13802-1-konstantin.ananyev@intel.com>

On Fri, May 21, 2021 at 03:42:07PM +0100, Konstantin Ananyev wrote:
<snip>
I apply this patch but it caused i40e pmd avx512 build failure. 
not sure about the root cause. I build debug version with latest repo. 




  reply	other threads:[~2021-05-21 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 14:42 Konstantin Ananyev
2021-05-21 14:55 ` Liang Ma [this message]
2021-05-21 15:10 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2021-05-21 15:16   ` Ananyev, Konstantin
2021-05-21 15:21   ` Liang Ma
2021-06-17  6:57 ` 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=YKfJ/olz/QgDR8A3@C02F33EJML85 \
    --to=liangma@liangbit.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).