On 9/17/2020 1:13 AM, Ajit Khaparde wrote:
On Wed, Sep 16, 2020 at 4:58 PM Ferruh Yigit <ferruh.yi...@intel.com> wrote:
On 9/16/2020 5:21 PM, Ajit Khaparde wrote:
On Tue, Sep 15, 2020 at 9:28 PM Ajit Khaparde
<ajit.khapa...@broadcom.com> 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.
