From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1F2DAA04B6; Thu, 17 Sep 2020 09:39:59 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id F0D521D53D; Thu, 17 Sep 2020 09:39:57 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 318F11D446 for ; Thu, 17 Sep 2020 09:39:56 +0200 (CEST) IronPort-SDR: ctn0lO5y9wIIUePP1wI16l2UwKi3DSh962lRaLobjZqvq6nVuVvGe59MKsat01GSgpFj/Yq0pI hkWAOs2k0fUA== X-IronPort-AV: E=McAfee;i="6000,8403,9746"; a="157051186" X-IronPort-AV: E=Sophos;i="5.76,436,1592895600"; d="scan'208";a="157051186" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Sep 2020 00:39:55 -0700 IronPort-SDR: H4E8oB6HyC2UIOIQUAi2RzQZNZtF7Hr6eH69546ViGKM6X+BL15l6JAAopBzgzwLsw8wAJC5fT bzFRHGxSNA4A== X-IronPort-AV: E=Sophos;i="5.76,436,1592895600"; d="scan'208";a="483636350" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.251.82.126]) ([10.251.82.126]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Sep 2020 00:39:53 -0700 To: Ajit Khaparde Cc: dpdk-dev References: <20200911015603.88359-1-ajit.khaparde@broadcom.com> <20200916042851.32914-1-ajit.khaparde@broadcom.com> <08c91475-0125-ff03-8bc2-ff38d5156519@intel.com> From: Ferruh Yigit Message-ID: <5701e2b4-7cd5-06bc-55bd-1b2088d9e9c8@intel.com> Date: Thu, 17 Sep 2020 08:39:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v2 00/25] patchset for bnxt X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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 9/17/2020 1:13 AM, Ajit Khaparde wrote: > On Wed, Sep 16, 2020 at 4:58 PM Ferruh Yigit wrote: >> >> On 9/16/2020 5:21 PM, Ajit Khaparde wrote: >>> On Tue, Sep 15, 2020 at 9:28 PM Ajit Khaparde >>> wrote: >>>> >>>> Some fixes and enhancements in the PMD and TruFlow layers. >>>> >>>> v1->v2: >>>> - rebased to latest >>>> - updated commit messages >>> Applied to dpdk-next-net-brcm. >>> >>>> >>>> Kishore Padmanabha (14): >>>> net/bnxt: fix port stop process and cleanup resources >>>> net/bnxt: fix the drop action flow to support count >>>> net/bnxt: reject flow offload with invalid MAC >>>> net/bnxt: reduce debug log messages >>>> net/bnxt: fix coexistence of ipv4 and ipv6 ingress rules >>>> net/bnxt: modify default flow rule creation >>>> net/bnxt: fix the function id used in flow flush >>>> net/bnxt: refactor VFR port clean up >>>> net/bnxt: remove VLAN pop action for egress flows >>>> net/bnxt: increase counter support from 8K to 16K >>>> net/bnxt: enable VXLAN ipv6 encapsulation >>>> net/bnxt: enable NAT action with tagged traffic >>>> net/bnxt: fix out of bound access in bit handling >>>> net/bnxt: add locks in flow database >>>> >>>> Mike Baucom (1): >>>> net/bnxt: free the EM index on failure >>>> >>>> Randy Schacher (1): >>>> net/bnxt: use direct HWRM message for interface table >>>> >>>> Shahaji Bhosle (2): >>>> net/bnxt: add null pointer check for resource manager >>>> net/bnxt: update resource settings >>>> >>>> Somnath Kotur (6): >>>> net/bnxt: fix crash in VFR queue select >>>> net/bnxt: fix VFR cleanup during init failure >>>> net/bnxt: check and set initial counter ID >>>> net/bnxt: fix bugs in representor data path >>>> net/bnxt: fix to check VNIC in shutdown path >>>> net/bnxt: add separate mutex for FW health check >>>> >>>> Sriharsha Basavapatna (1): >>>> net/bnxt: provide switch info if VFR are configured >>>> >> >> Hi Ajit, >> >> I assume the backporting of the majority of the patchset explicitly not >> requested, since two of them has stable tag but rest don't, but I would >> like to confirm. >> >> And I suggest backporting fixes as much as possible, since missing some >> fixes may cause conflict for future fixes and prevent backporting them. > Hi Ferruh, > Most of the fixes are actually for changes made in 20.08 > Since it is not an LTS, I think not really porting them should not be a problem. > But if there is any patch which needs to go into earlier LTS releases, > I will add it to the list of backports. > This is not just for LTS, if somehow we have 20.08.1, they will matter. Also this is good for documenting the actual intention of the author related backporting the patches. As far as I can see there is not explicit request to "not" backport them, so I will add the missing tags while merging.