From: Vincent Chen <vincent.chen@sifive.com>
To: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
vincent.chen@sifive.com
Subject: [PATCH 0/2] ice: fix VF creation when !CONFIG_ICE_SWITCHDEV
Date: Wed, 29 Apr 2026 14:51:25 +0800 [thread overview]
Message-ID: <20260429065127.423949-1-vincent.chen@sifive.com> (raw)
This patch series fixes an issue where VF creation fails when
CONFIG_ICE_SWITCHDEV is disabled.
When CONFIG_ICE_SWITCHDEV is disabled, the stub function
ice_eswitch_attach_vf() returns -EOPNOTSUPP, causing VF initialization to
fail even though basic VF functionality should work without switchdev
support.
The fix is split into two patches:
1. Add switchdev mode checks at caller sites to fix the immediate
issue while maintaining backward compatibility. This ensures
ice_eswitch_attach_vf() is only called when switchdev mode is
enabled, consistent with how ice_eswitch_attach_sf() is handled.
2. Remove the now-redundant internal switchdev check from
ice_eswitch_attach_vf().
Vincent Chen (2):
ice: allow creating VFs when !CONFIG_ICE_SWITCHDEV
ice: remove redundant switchdev check in ice_eswitch_attach_vf()
drivers/net/ethernet/intel/ice/ice_eswitch.c | 3 ---
drivers/net/ethernet/intel/ice/ice_sriov.c | 14 ++++++++------
drivers/net/ethernet/intel/ice/ice_vf_lib.c | 3 ++-
3 files changed, 10 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2026-04-29 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 6:51 Vincent Chen [this message]
2026-04-29 6:51 ` [PATCH 1/2] ice: allow creating VFs when !CONFIG_ICE_SWITCHDEV Vincent Chen
2026-04-29 9:17 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-29 6:51 ` [PATCH 2/2] ice: remove redundant switchdev check in ice_eswitch_attach_vf() Vincent Chen
2026-04-29 9:18 ` [Intel-wired-lan] " Loktionov, Aleksandr
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=20260429065127.423949-1-vincent.chen@sifive.com \
--to=vincent.chen@sifive.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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