patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Ali Alnubani <alialnu@nvidia.com>, Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk stable <stable@dpdk.org>, dev <dev@dpdk.org>,
	 Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	Akhil Goyal <akhil.goyal@nxp.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>,
	Ian Stokes <ian.stokes@intel.com>,
	 Jerin Jacob <jerinj@marvell.com>,
	John McNamara <john.mcnamara@intel.com>,
	 Ju-Hyoung Lee <juhlee@microsoft.com>,
	Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	 "Yu, PingX" <pingx.yu@intel.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	 Raslan Darawsheh <rasland@nvidia.com>,
	NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	 "Peng, Yuan" <yuan.peng@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] 19.11.9 patches review and test - V2
Date: Thu, 10 Jun 2021 12:05:44 +0200
Message-ID: <CAATJJ0+32pH5qpwRWgi2tkZ5edmq+iDaREY_rWXScZ_sy4PSSg@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB51673907F223F46DAC8CC109DA359@DM4PR12MB5167.namprd12.prod.outlook.com>

On Thu, Jun 10, 2021 at 11:05 AM Ali Alnubani <alialnu@nvidia.com> wrote:
>
> Hi Christian,
>
> > -----Original Message-----
> > From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > Sent: Thursday, June 10, 2021 11:49 AM
> > To: dpdk stable <stable@dpdk.org>
> > Cc: dev <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>; Ian Stokes <ian.stokes@intel.com>; Jerin
> > Jacob <jerinj@marvell.com>; John McNamara <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>; Yu, PingX <pingx.yu@intel.com>; Xu, Qian Q
> > <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@nvidia.com>; NBU-
> > Contact-Thomas Monjalon <thomas@monjalon.net>; Peng, Yuan
> > <yuan.peng@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> > Subject: Re: [dpdk-dev] 19.11.9 patches review and test - V2
> >
> > On Fri, Jun 4, 2021 at 7:52 AM Christian Ehrhardt
> > <christian.ehrhardt@canonical.com> wrote:
> > >
> > > Hi all,
> > >
> > > Here is version 2 of the list of patches targeted for stable release 19.11.9.
> > > Thanks to plenty of helpful developers we've collected a few more
> > > backports by now and sorted out a few rare compile time issues that were
> > found with -rc1.
> > >
> > > The planned date for the final release of 19.11.9 is now 18th of June.
> > >
> > > 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.9-rc2
> >
> > Unfortunately there were further build issues with new suse kernels.
> > The fix for some of them, now breaks others :-/ The final fix didn't finalize
> > yet, but as a TL;DR it means there will be a -rc3 down the road.
> >
> > I beg your pardon for the extra work.
> > If you are testing non-suse and are already deep into the tests you likely can
> > continue that.
> > If you didn't start your tests yet then I'd recommend holding back until -rc3
> > exists.
> >
>
> I see some build failures with gcc 11. Do we expect this release to support it?

I have added all that were targeted at stable@dpdk, but I remember
that Kevin mentioned a few missing in 20.11.x due to the submissions
missing to go to stable@dpdk.
The same could be the case here.
@Kevin could you have a look at 19.11 and if there are some missing
point me to the commits to pick up?

@Ali - if you have a particular bug signature that might help to
identify the right patch.

> I also see some doxygen errors with version 1.9.1 in Fedora Rawhide. Will open a Bugzilla ticket.

Rawhide builds of 19.11.x were broken for a while now, but yeah filing
the bug surely is the right path.

> Thanks,
> Ali



-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2021-06-10 10:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  5:52 [dpdk-stable] " Christian Ehrhardt
2021-06-10  8:48 ` [dpdk-stable] [dpdk-dev] " Christian Ehrhardt
2021-06-10  9:05   ` Ali Alnubani
2021-06-10 10:05     ` Christian Ehrhardt [this message]
2021-06-10 10:29       ` Kevin Traynor
2021-06-10 10:58         ` Christian Ehrhardt
2021-06-10 11:18           ` Ali Alnubani
2021-06-10 11:02         ` Kevin Traynor
2021-06-10 13:56           ` Christian Ehrhardt
2021-06-11  8:55             ` Jiang, YuX
2021-06-14  5:20               ` Christian Ehrhardt
2021-06-14 12:21                 ` Luc Pelletier
2021-06-10 11:00   ` Christian Ehrhardt
2021-06-15  3:17 ` [dpdk-stable] " Pei Zhang
2021-06-15  7:05   ` 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=CAATJJ0+32pH5qpwRWgi2tkZ5edmq+iDaREY_rWXScZ_sy4PSSg@mail.gmail.com \
    --to=christian.ehrhardt@canonical.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=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

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git