From: "Jiang, YuX" <yux.jiang@intel.com>
To: "christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
"Ali Alnubani" <alialnu@nvidia.com>,
"Walker, Benjamin" <benjamin.walker@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
"Govindharajan, Hariprasad" <hariprasad.govindharajan@intel.com>,
"Hemant Agrawal" <hemant.agrawal@nxp.com>,
"Stokes, Ian" <ian.stokes@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
"pingx.yu@intel.com" <pingx.yu@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: RE: 19.11.11 patches review and test
Date: Tue, 14 Dec 2021 07:14:17 +0000 [thread overview]
Message-ID: <BYAPR11MB27111442BA65C798B61BCC34FE759@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211209144315.3424225-1-christian.ehrhardt@canonical.com>
> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
> Sent: Thursday, December 9, 2021 10:43 PM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani <alialnu@nvidia.com>;
> Walker, Benjamin <benjamin.walker@intel.com>; David Christensen
> <drc@linux.vnet.ibm.com>; Govindharajan, Hariprasad
> <hariprasad.govindharajan@intel.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Stokes, Ian <ian.stokes@intel.com>; Jerin
> Jacob <jerinj@marvell.com>; Mcnamara, John <john.mcnamara@intel.com>;
> Ju-Hyoung Lee <juhlee@microsoft.com>; Kevin Traynor
> <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>; Pei Zhang
> <pezhang@redhat.com>; pingx.yu@intel.com; Xu, Qian Q
> <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@nvidia.com>; Thomas
> Monjalon <thomas@monjalon.net>; Peng, Yuan <yuan.peng@intel.com>;
> Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Subject: 19.11.11 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 19.11.11.
>
> The planned date for the final release is 7th January 2021.
>
> Please help with testing and validation of your use cases and report any
> issues/results with reply-all to this mail. For the final release the fixes and
> reported validations will be added to the release notes.
>
> A release candidate tarball can be found at:
>
> https://dpdk.org/browse/dpdk-stable/tag/?id=v19.11.11-rc1
>
> These patches are located at branch 19.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
> ---
Hi Christian,
We find many build issues on LTS19.11. But all of them have no fix yet.
https://bugs.dpdk.org/show_bug.cgi?id=744 DPDK core dev UNCO --- [dpdk-19.11.9-rc3] make build failed on Fedora34 with GCC11 and build failed on Fedora35 with gcc11.2.1&clang13.0.0
https://bugs.dpdk.org/show_bug.cgi?id=747 DPDK core dev UNCO --- [dpdk-19.11.9-rc3] Meson build failed with ICC-19.1.1
https://bugs.dpdk.org/show_bug.cgi?id=900 DPDK ethdev dev UNCO --- [19.11.11-rc1] net/nfp build failure with clang 13
https://bugs.dpdk.org/show_bug.cgi?id=901 DPDK ethdev dev UNCO --- [19.11.11-rc1] net/i40e build failure with make and clang 13
https://bugs.dpdk.org/show_bug.cgi?id=902 DPDK ethdev dev UNCO --- [19.11.11-rc1] net/ice build failure with make and clang 13
https://bugs.dpdk.org/show_bug.cgi?id=903 DPDK ethdev dev UNCO --- [19.11.11-rc1] net/ixgbe build failure with make and clang 13
https://bugs.dpdk.org/show_bug.cgi?id=904 DPDK meson dev UNCO --- [dpdk-19.11.11] Meson build has some failures on Fedora35 with clang 13.0.0
https://bugs.dpdk.org/show_bug.cgi?id=905 DPDK meson dev UNCO --- [dpdk-19.11.11-rc1]Meson&Makefile build failed on Freebsd13 with gcc10.3.0&clang11.0.1
next prev parent reply other threads:[~2021-12-14 7:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 14:43 christian.ehrhardt
2021-12-13 4:14 ` Kalesh Anakkur Purayil
2021-12-13 11:06 ` Ferruh Yigit
2021-12-13 12:39 ` Christian Ehrhardt
2021-12-13 12:58 ` Ferruh Yigit
2021-12-13 13:32 ` Christian Ehrhardt
2021-12-13 13:49 ` Kalesh Anakkur Purayil
2021-12-13 14:07 ` Ferruh Yigit
2021-12-14 5:49 ` Kalesh Anakkur Purayil
2021-12-14 7:44 ` Christian Ehrhardt
2021-12-14 10:13 ` Ferruh Yigit
2021-12-14 11:39 ` Christian Ehrhardt
2021-12-14 12:08 ` Ferruh Yigit
2021-12-14 13:57 ` Christian Ehrhardt
2021-12-14 13:10 ` Ferruh Yigit
2021-12-14 13:58 ` Christian Ehrhardt
2021-12-14 14:46 ` Christian Ehrhardt
2021-12-14 14:52 ` Ferruh Yigit
2021-12-15 13:17 ` Christian Ehrhardt
2021-12-15 14:44 ` Ferruh Yigit
2021-12-16 7:21 ` Christian Ehrhardt
2021-12-14 7:14 ` Jiang, YuX [this message]
2021-12-14 7:45 ` Christian Ehrhardt
2021-12-14 8:05 ` Christian Ehrhardt
2021-12-15 11:04 ` Jiang, YuX
2021-12-15 13:16 ` Christian Ehrhardt
2021-12-17 7:05 ` Jiang, YuX
2021-12-17 7:47 ` Christian Ehrhardt
2021-12-14 13:51 ` Pei Zhang
2021-12-14 13:52 ` Christian Ehrhardt
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=BYAPR11MB27111442BA65C798B61BCC34FE759@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=ktraynor@redhat.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).