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 1CC18A0C45; Thu, 10 Jun 2021 15:57:13 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9365D4067C; Thu, 10 Jun 2021 15:57:12 +0200 (CEST) Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by mails.dpdk.org (Postfix) with ESMTP id 781724003C for ; Thu, 10 Jun 2021 15:57:10 +0200 (CEST) Received: from mail-qv1-f71.google.com ([209.85.219.71]) by youngberry.canonical.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1lrLBF-00006i-Ks for dev@dpdk.org; Thu, 10 Jun 2021 13:57:09 +0000 Received: by mail-qv1-f71.google.com with SMTP id br4-20020ad446a40000b029021addf7b587so20336659qvb.10 for ; Thu, 10 Jun 2021 06:57:09 -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=C969W1QOYdwCCz+ahSJdEtd6UhdciyMO+3a7pO5rohA=; b=KaHp/zBJnkY/DlQRYuwHv/RJgNCg5WMNJg2N2uG+FBWtsz/sqXyRo9US0Yf957EmNX B/vvsJMATXqjUUeMcB5vo5BWmpftPNT7v/RmZawdgw34ZzfeX8bB/3ffQPpjbti0nxei 7rZeMIeghl2e0gsTyDvQ5tvqr1YGyM9Gt27GbJSalKJU/eUEn6hJ7xCGxd4shlvdRSay R8DHQAxi7kVVEwLrBCEwCpm4HXo8saBRJvdg21I+6ab8xxbEqn02lbacUcC2n9F3PsWB xqQ39dsLeiHNM0W+WeMLT7k3pOVlFE1J+VDQgg0g/OmtNklziN5nAh/gYul6hLlCmjDq CW1A== X-Gm-Message-State: AOAM530GjJ5tPQniZ712n9rfsfFjMMPOH/n4syGUurfJJHROf9vbmSdT N5rgf0+7E6Ttp0x1zabwLbsQlGrrxQe+MaglWeLT+ugAxJzc78tv+fcRE2p5XgsWA4wshI6UjTG +VPUTzNiKkq6sUbIFz7MUJr/kVFzQD1rv/hML X-Received: by 2002:ac8:5708:: with SMTP id 8mr5205050qtw.112.1623333428727; Thu, 10 Jun 2021 06:57:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz+76mZat8vzfZEFyB6FZhxJBgBQw+bX0A3y0ZF6JBl/88ggTzdfgPDoNP9ePSZY7X38o2NZNK+bR8nCp0bPl0= X-Received: by 2002:ac8:5708:: with SMTP id 8mr5205013qtw.112.1623333428488; Thu, 10 Jun 2021 06:57:08 -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 15:56:42 +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-dev] 19.11.9 patches review and test - V2 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jun 10, 2021 at 1:03 PM Kevin Traynor wrote: > > 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 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 > ^ just sent backport of this with upstream commit and correct tag > http://inbox.dpdk.org/stable/20210610110028.230803-1-ktraynor@redhat.com/T/#u I've already applied it a few hours ago, but the content is the same > > 414245bbc5 test/cmdline: fix inputs array > ^ this one was already merged on 19.11 and 20.11 branches Yes, as are all the other GCC 11 fixes we discussed. Thank you Kevin! > > > >>> 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