From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D6172A0C42 for ; Thu, 10 Jun 2021 12:59:27 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BE1C5410FD; Thu, 10 Jun 2021 12:59:25 +0200 (CEST) Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by mails.dpdk.org (Postfix) with ESMTP id 9CD034003C for ; Thu, 10 Jun 2021 12:59:23 +0200 (CEST) Received: from mail-qk1-f200.google.com ([209.85.222.200]) by youngberry.canonical.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1lrIPC-0002SC-WD for stable@dpdk.org; Thu, 10 Jun 2021 10:59:23 +0000 Received: by mail-qk1-f200.google.com with SMTP id 81-20020a370e540000b02903aacdbd70b7so2614163qko.23 for ; Thu, 10 Jun 2021 03:59:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HExreClNcqHLHT52aPpgU5P4+JJQYhGb0Tj25wd9e5c=; b=R4/Ha8W9dTauS70MENsYyP8MvMo8OWD4+sUkxKKRA2sNLesT4PXOcFZG0YRVHNT6EU 7x7mc8kIdBlGLhOPs+vgluHy0dAAHxDjFOv0urjxgaDPqt1q0twlT7OCTMy+moe+Lgw6 /QvEkavpSe2OlIrdIdT+5esku36xZR46wYFw5OgfnD/CrEd6Ozn+JKrgF3exbCQQ9N5Z Lo3oWLE5O8j+J9eBtyuiUEDqQ1qUEqPxFapfHhzANagSOFCnkbjVArgkU81jdU2EQX+K +VviftpW0Eo2IDNnvzzxIDn5PRYV7mHFyz0318TVKQJfqEVCOWslxHm8R1gi7idI1/Vk /P/w== X-Gm-Message-State: AOAM533y9+UxtGomgEcThHoguERKAtmhMw9myWDt+ujBlQFNSoTZ2f4E Nv01gpkEvWsJxRqUo/Un7JyGmxJPaDaMdlGbO/oS02acKNpxp39LZ//V95uS7vkQXFtybeWask+ MYD3ZUQwxbUjenBREj3cqnK3mUvb8yTE6fbRanIRK X-Received: by 2002:a0c:c3d1:: with SMTP id p17mr4509688qvi.44.1623322762117; Thu, 10 Jun 2021 03:59:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxftDJWnQWh7MhXgPDncOjBVA4Grha3vhOnirs6UsR/Oo7sqvKvAnjytt/mijom+KTqM2aOYGXFophNfVFz5Qo= X-Received: by 2002:a0c:c3d1:: with SMTP id p17mr4509668qvi.44.1623322761844; Thu, 10 Jun 2021 03:59:21 -0700 (PDT) MIME-Version: 1.0 References: <20210604055236.2900938-1-christian.ehrhardt@canonical.com> In-Reply-To: From: Christian Ehrhardt Date: Thu, 10 Jun 2021 12:58:55 +0200 Message-ID: To: Kevin Traynor Cc: Ali Alnubani , dpdk stable , dev , Abhishek Marathe , Akhil Goyal , "Walker, Benjamin" , David Christensen , "Govindharajan, Hariprasad" , Hemant Agrawal , Ian Stokes , Jerin Jacob , John McNamara , Ju-Hyoung Lee , Luca Boccassi , Pei Zhang , "Yu, PingX" , "Xu, Qian Q" , Raslan Darawsheh , NBU-Contact-Thomas Monjalon , "Peng, Yuan" , "Chen, Zhaoyan" Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-stable] [dpdk-dev] 19.11.9 patches review and test - V2 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On Thu, Jun 10, 2021 at 12:30 PM Kevin Traynor wrote: > > On 10/06/2021 11:05, Christian Ehrhardt wrote: > > On Thu, Jun 10, 2021 at 11:05 AM Ali Alnubani wrote: > >> > >> Hi Christian, > >> > >>> -----Original Message----- > >>> From: Christian Ehrhardt > >>> Sent: Thursday, June 10, 2021 11:49 AM > >>> To: dpdk stable > >>> Cc: dev ; Abhishek Marathe > >>> ; Akhil Goyal ; > >>> Ali Alnubani ; Walker, Benjamin > >>> ; David Christensen > >>> ; Govindharajan, Hariprasad > >>> ; Hemant Agrawal > >>> ; Ian Stokes ; Jerin > >>> Jacob ; John McNamara ; > >>> Ju-Hyoung Lee ; Kevin Traynor > >>> ; Luca Boccassi ; Pei Zhang > >>> ; Yu, PingX ; Xu, Qian Q > >>> ; Raslan Darawsheh ; NBU- > >>> Contact-Thomas Monjalon ; Peng, Yuan > >>> ; Chen, Zhaoyan > >>> Subject: Re: [dpdk-dev] 19.11.9 patches review and test - V2 > >>> > >>> On Fri, Jun 4, 2021 at 7:52 AM Christian Ehrhardt > >>> 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 > 414245bbc5 test/cmdline: fix inputs array Compiler patches in main: I've rechecked all those to see why they were missing (if they did) to find if anything else is missing as well. GCC: 71acf81bf7 doc: add GCC 11 and clang 12 support to release notes - not targetted at stable (ok to be missing) 50eea2bfa7 test: fix build with GCC 11 - this got all missed due to the same problem Xueming had reported 099db3d156 crypto/zuc: fix build with GCC 11 - fixed code is only in 20.05 8f73a72378 test/crypto: fix build with GCC 11 33c12ac5ba test/table: fix build with GCC 11 a625ab89df net/tap: fix build with GCC 11 97de3819ed net/ice/base: fix build with GCC 11 ab70be7e2d net/bnx2x: fix build with GCC 11 b3c740e037 net/bnx2x: fix build with GCC 11 - these got all missed due to the same problem Xueming had reported 8e2dd74f0a acl: fix build with GCC 11 - I've seen this one but it fixes code that is only in 20.11 Clang: 5ac070cfed test/cmdline: silence clang 12 warning 414245bbc5 test/cmdline: fix inputs array Those two just were not tagged, that is fine and they will be added this round. I was able to identify quite a few more affected by the same issue So I thank you a lot for pushing on this! > >> 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