On 10/06/2021 11:29, Kevin Traynor wrote: > On 10/06/2021 11:05, Christian Ehrhardt wrote: >> On Thu, Jun 10, 2021 at 11:05 AM Ali Alnubani <[email protected]> wrote: >>> >>> Hi Christian, >>> >>>> -----Original Message----- >>>> From: Christian Ehrhardt <[email protected]> >>>> Sent: Thursday, June 10, 2021 11:49 AM >>>> To: dpdk stable <[email protected]> >>>> Cc: dev <[email protected]>; Abhishek Marathe >>>> <[email protected]>; Akhil Goyal <[email protected]>; >>>> Ali Alnubani <[email protected]>; Walker, Benjamin >>>> <[email protected]>; David Christensen >>>> <[email protected]>; Govindharajan, Hariprasad >>>> <[email protected]>; Hemant Agrawal >>>> <[email protected]>; Ian Stokes <[email protected]>; Jerin >>>> Jacob <[email protected]>; John McNamara <[email protected]>; >>>> Ju-Hyoung Lee <[email protected]>; Kevin Traynor >>>> <[email protected]>; Luca Boccassi <[email protected]>; Pei Zhang >>>> <[email protected]>; Yu, PingX <[email protected]>; Xu, Qian Q >>>> <[email protected]>; Raslan Darawsheh <[email protected]>; NBU- >>>> Contact-Thomas Monjalon <[email protected]>; Peng, Yuan >>>> <[email protected]>; Chen, Zhaoyan <[email protected]> >>>> Subject: Re: [dpdk-dev] 19.11.9 patches review and test - V2 >>>> >>>> On Fri, Jun 4, 2021 at 7:52 AM Christian Ehrhardt >>>> <[email protected]> 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. >> > > They will all note 'GCC' (or gcc) in the commit msg. Most will have an > example of the 'warning' they resolved too. There was also bugzillas > opened for them all i think, which note the fixing commit. So if you > find any issues when building, you could cross-reference between warning > in commit/warning in Bz and fixing commit. Of course there may be some > new issues pop up in older code that was later changed/replaced in main. > > There was also 2 commits needed for clang 12 support (my bad for missing > tags on these).
> 5ac070cfed test/cmdline: silence clang 12 warning ^ just sent backport of this with upstream commit and correct tag http://inbox.dpdk.org/stable/[email protected]/T/#u > 414245bbc5 test/cmdline: fix inputs array ^ this one was already merged on 19.11 and 20.11 branches > >>> 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 >> >> >> >
