From: Simon Horman <horms@kernel.org>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, pavan.chebbi@broadcom.com,
andrew.gospodarek@broadcom.com,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Subject: Re: [PATCH net-next 3/9] bnxt_en: Support QOS and TPID settings for the SRIOV VLAN
Date: Mon, 15 Jul 2024 10:17:36 +0100 [thread overview]
Message-ID: <20240715091736.GD8432@kernel.org> (raw)
In-Reply-To: <20240713234339.70293-4-michael.chan@broadcom.com>
On Sat, Jul 13, 2024 at 04:43:33PM -0700, Michael Chan wrote:
> From: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
>
> With recent changes in the .ndo_set_vf_*() guidelines, resubmitting
> this patch that was reverted eariler in 2023:
>
> c27153682eac ("Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN")
I acknowledge there was a policy change and thus
this feature can now be accepted.
- [net-next,v2] docs: net: document guidance of implementing the SR-IOV NDOs
https://git.kernel.org/netdev/net-next/c/4558645d139c
>
> Add these missing settings in the .ndo_set_vf_vlan() method.
> Older firmware does not support the TPID setting so check for
> proper support.
>
> Remove the unused BNXT_VF_QOS flag.
>
> Signed-off-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Reviewed-by: Simon Horman <horms@kernel.org>
...
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.c b/drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.c
...
> @@ -256,21 +254,21 @@ int bnxt_set_vf_vlan(struct net_device *dev, int vf_id, u16 vlan_id, u8 qos,
> if (bp->hwrm_spec_code < 0x10201)
> return -ENOTSUPP;
>
> - if (vlan_proto != htons(ETH_P_8021Q))
> + if (vlan_proto != htons(ETH_P_8021Q) &&
> + (vlan_proto != htons(ETH_P_8021AD) ||
nit: As a follow-up this could be updated to use eth_type_vlan()
> + !(bp->fw_cap & BNXT_FW_CAP_DFLT_VLAN_TPID_PCP)))
> return -EPROTONOSUPPORT;
>
> rc = bnxt_vf_ndo_prep(bp, vf_id);
> if (rc)
> return rc;
...
next prev parent reply other threads:[~2024-07-15 9:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 23:43 [PATCH net-next 0/9] bnxt_en: Update for net-next Michael Chan
2024-07-13 23:43 ` [PATCH net-next 1/9] bnxt_en: add support for storing crash dump into host memory Michael Chan
2024-07-15 9:28 ` Simon Horman
2024-07-13 23:43 ` [PATCH net-next 2/9] bnxt_en: add support for retrieving crash dump using ethtool Michael Chan
2024-07-15 9:28 ` Simon Horman
2024-07-13 23:43 ` [PATCH net-next 3/9] bnxt_en: Support QOS and TPID settings for the SRIOV VLAN Michael Chan
2024-07-15 9:17 ` Simon Horman [this message]
2024-07-13 23:43 ` [PATCH net-next 4/9] bnxt_en: Deprecate support for legacy INTX mode Michael Chan
2024-07-15 9:28 ` Simon Horman
2024-07-15 16:24 ` Michael Chan
2024-07-16 16:57 ` Dan Carpenter
2024-07-16 17:28 ` Michael Chan
2024-07-13 23:43 ` [PATCH net-next 5/9] bnxt_en: Remove BNXT_FLAG_USING_MSIX flag Michael Chan
2024-07-15 9:29 ` Simon Horman
2024-07-15 17:32 ` Bjorn Helgaas
2024-07-15 18:00 ` Michael Chan
2024-07-13 23:43 ` [PATCH net-next 6/9] bnxt_en: Remove register mapping to support INTX Michael Chan
2024-07-15 9:30 ` Simon Horman
2024-07-15 17:27 ` Bjorn Helgaas
2024-07-13 23:43 ` [PATCH net-next 7/9] bnxt_en: Replace deprecated PCI MSIX APIs Michael Chan
2024-07-15 9:30 ` Simon Horman
2024-07-13 23:43 ` [PATCH net-next 8/9] bnxt_en: Allocate the max bp->irq_tbl size for dynamic msix allocation Michael Chan
2024-07-15 9:30 ` Simon Horman
2024-07-15 17:33 ` Bjorn Helgaas
2024-07-13 23:43 ` [PATCH net-next 9/9] bnxt_en: Support dynamic MSIX Michael Chan
2024-07-15 9:31 ` Simon Horman
2024-07-15 17:34 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240715091736.GD8432@kernel.org \
--to=horms@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).