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 AD3D1A0C49; Thu, 10 Jun 2021 12:30:09 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7DA0F40E64; Thu, 10 Jun 2021 12:30:09 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 13DA04003C for ; Thu, 10 Jun 2021 12:30:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623321005; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=l5chq/2jcuaGE4/eBfjcv3JAz/lVyA15w8ZgsmJWEyc=; b=c6CoKHKRIG59ZJZIvGlBnmdVgqd/ijPfK7OBdnQF12BBBawcNhN9dCkGilVmrX+CI/hpnc 1fgIkx8IW7q/kWGEv86KG0LE8F+xliMRyLxa/v9zKy0LzUDJIcyQ22NWbhKk38Uc1dDsLs ys8tlZsU5OMtekjRorg2AbvXVjemvoM= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-451-yZRe1WcJNqSk_n9f2bTenw-1; Thu, 10 Jun 2021 06:30:02 -0400 X-MC-Unique: yZRe1WcJNqSk_n9f2bTenw-1 Received: by mail-wr1-f71.google.com with SMTP id g14-20020a5d698e0000b0290117735bd4d3so670348wru.13 for ; Thu, 10 Jun 2021 03:30:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:references:from:subject:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=l5chq/2jcuaGE4/eBfjcv3JAz/lVyA15w8ZgsmJWEyc=; b=D4Z0ZXAW78uGGAfQKf+3gwvUc8sCtdWyMOSl2LtDREBpdPhi+SIeeIC6ynmKS2kDiq lA0s0/gXXgbY1ioM2UKv0ZvZ679US7zskZulQhtVYiIuXoC/rYuCP/GJgR2LSJqQ1L3J co3W+PL3UXnb+b5dHoblRti3vFNVJVWq2BlFrURJAZ2csiWZXfuHm9c6wGyEyPl4WefG vLbpcbssjyIRTzbLebux6LAjnQMuqnsVWT4sCb3FbChIXIIP+7CTZYEDgg162WQSiqHO BZYsphUkuGuWNHACTBW8E2DN4Gy2j7venweJ7iBNqU+slXYcodML8YCApoIONcj0sFGT 0FJw== X-Gm-Message-State: AOAM5313eqkacc7JQZH5boWTt2qGtZw/0sckOzFJwYeIbvtRxSLdb2cB 4cG5NRnIBlN6R1ANRj8+NP7pKN25CPtu+XGflHX7DbL5bgm82Erz3yqrF+4DmM+spaKRYb5wEWs DZ3I= X-Received: by 2002:a5d:6b0e:: with SMTP id v14mr4583282wrw.297.1623321001301; Thu, 10 Jun 2021 03:30:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwa7T+JovK0v+r4eYWVJRpIv7UNTUTl1nfjr8+gYHPgMbvZ3qUJZB5JfZ0SCLRt8IMnLuFZdg== X-Received: by 2002:a5d:6b0e:: with SMTP id v14mr4583265wrw.297.1623321001143; Thu, 10 Jun 2021 03:30:01 -0700 (PDT) Received: from [192.168.0.36] ([78.17.79.77]) by smtp.gmail.com with ESMTPSA id m132sm2538271wmf.10.2021.06.10.03.29.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Jun 2021 03:30:00 -0700 (PDT) To: Christian Ehrhardt , Ali Alnubani Cc: 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" References: <20210604055236.2900938-1-christian.ehrhardt@canonical.com> From: Kevin Traynor Message-ID: Date: Thu, 10 Jun 2021 11:29:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ktraynor@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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 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 >> 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 > > >