From: Jiri Pirko <jiri@resnulli.us>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: wojciech.drewek@intel.com, netdev@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [iwl-next v1] ice: use internal pf id instead of function number
Date: Wed, 14 Aug 2024 15:51:20 +0200 [thread overview]
Message-ID: <Zry2WL9JFtz4Q-N1@nanopsycho.orion> (raw)
In-Reply-To: <20240813071610.52295-1-michal.swiatkowski@linux.intel.com>
Tue, Aug 13, 2024 at 09:16:10AM CEST, michal.swiatkowski@linux.intel.com wrote:
>Use always the same pf id in devlink port number. When doing
>pass-through the PF to VM bus info func number can be any value.
From the patch subject I'm not sure which tree you target, but since
this is a bugfix of something not recent, you should target -net.
Also, please provide "Fixes" tag blaming the commit(s) that introduced
the issue.
>
>Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
>Suggested-by: Jiri Pirko <jiri@resnulli.us>
>Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>---
> drivers/net/ethernet/intel/ice/devlink/devlink_port.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/net/ethernet/intel/ice/devlink/devlink_port.c b/drivers/net/ethernet/intel/ice/devlink/devlink_port.c
>index 4abdc40d345e..1fe441bfa0ca 100644
>--- a/drivers/net/ethernet/intel/ice/devlink/devlink_port.c
>+++ b/drivers/net/ethernet/intel/ice/devlink/devlink_port.c
>@@ -340,7 +340,7 @@ int ice_devlink_create_pf_port(struct ice_pf *pf)
> return -EIO;
>
> attrs.flavour = DEVLINK_PORT_FLAVOUR_PHYSICAL;
>- attrs.phys.port_number = pf->hw.bus.func;
>+ attrs.phys.port_number = pf->hw.pf_id;
>
> /* As FW supports only port split options for whole device,
> * set port split options only for first PF.
>@@ -458,7 +458,7 @@ int ice_devlink_create_vf_port(struct ice_vf *vf)
> return -EINVAL;
>
> attrs.flavour = DEVLINK_PORT_FLAVOUR_PCI_VF;
>- attrs.pci_vf.pf = pf->hw.bus.func;
>+ attrs.pci_vf.pf = pf->hw.pf_id;
> attrs.pci_vf.vf = vf->vf_id;
>
> ice_devlink_set_switch_id(pf, &attrs.switch_id);
>--
>2.42.0
>
prev parent reply other threads:[~2024-08-14 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 7:16 [Intel-wired-lan] [iwl-next v1] ice: use internal pf id instead of function number Michal Swiatkowski
2024-08-14 13:51 ` Jiri Pirko [this message]
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=Zry2WL9JFtz4Q-N1@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=wojciech.drewek@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