DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Leyi Rong <leyi.rong@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Bruce Richardson <bruce.richardson@intel.com>,
	 Tal Shnaiderman <talshn@nvidia.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	 Pallavi Kadam <pallavi.kadam@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	 Ranjit Menon <ranjit.menon@intel.com>,
	Beilei Xing <beilei.xing@intel.com>, dev <dev@dpdk.org>,
	 Aaron Conole <aconole@redhat.com>,
	ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] fix mingw build error
Date: Tue, 2 Feb 2021 09:36:44 +0100	[thread overview]
Message-ID: <CAJFAV8wqzMKwfsJGai4otHUkDe=eV1YUQzb_NsOPvCPA9fNtPg@mail.gmail.com> (raw)
In-Reply-To: <2799531.7hoMMOPb9E@thomas>

On Thu, Jan 28, 2021 at 10:27 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 28/01/2021 13:28, David Marchand:
> > On Wed, Jan 27, 2021 at 3:47 PM Leyi Rong <leyi.rong@intel.com> wrote:
> > >
> > > This patchset fix mingw build error when avx512 is introduced.
> > >
> > > ---
> > > v2:
> > > - Set i40e_avx512_cc_support to false to avoid the build error under
> > >   windows with mingw.
> > >
> > > Leyi Rong (2):
> > >   config: disable avx512 on mingw cross build
> > >   net/i40e: fix mingw build error
> > >
> > >  config/x86/cross-mingw       | 3 +++
> > >  drivers/net/i40e/meson.build | 4 ++++
> > >  2 files changed, 7 insertions(+)
> >
> > LGTM with fc32 mingw.
> > Tested-by: David Marchand <david.marchand@redhat.com>
>
> Applied, thanks.
>
> Dmitry found a lighter alternative option to be tested and discussed.

We still have build failures at UNH for Windows, on the rc2 tag:
http://mails.dpdk.org/archives/test-report/2021-February/177464.html

Is this issue being looked at?


-- 
David Marchand


  reply	other threads:[~2021-02-02  8:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 15:38 [dpdk-dev] [PATCH] net/i40e: " Leyi Rong
2021-01-26 16:18 ` Kadam, Pallavi
2021-01-26 17:04 ` Tal Shnaiderman
2021-01-27  8:30   ` Rong, Leyi
2021-01-27  8:47 ` [dpdk-dev] [PATCH v2 0/2] " Leyi Rong
2021-01-27  8:47   ` [dpdk-dev] [PATCH v2 1/2] config: disable avx512 on mingw cross build Leyi Rong
2021-01-27  8:47   ` [dpdk-dev] [PATCH v2 2/2] net/i40e: fix mingw build error Leyi Rong
2021-01-27 10:40     ` Bruce Richardson
2021-01-27 12:18       ` Rong, Leyi
2021-01-27 14:27 ` [dpdk-dev] [PATCH v3 0/2] " Leyi Rong
2021-01-27 14:27   ` [dpdk-dev] [PATCH v3 1/2] config: disable avx512 on mingw cross build Leyi Rong
2021-01-27 14:27   ` [dpdk-dev] [PATCH v3 2/2] net/i40e: fix mingw build error Leyi Rong
2021-01-27 19:15   ` [dpdk-dev] [PATCH v3 0/2] " Kadam, Pallavi
2021-01-28 12:28   ` David Marchand
2021-01-28 21:26     ` Thomas Monjalon
2021-02-02  8:36       ` David Marchand [this message]
2021-02-02  9:09         ` Rong, Leyi

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='CAJFAV8wqzMKwfsJGai4otHUkDe=eV1YUQzb_NsOPvCPA9fNtPg@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=ferruh.yigit@intel.com \
    --cc=leyi.rong@intel.com \
    --cc=pallavi.kadam@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=talshn@nvidia.com \
    --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 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).