Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Kalyan Kodamagula <kalyan.kodamagula@intel.com>
Cc: Brett Creeley <brett.creeley@intel.com>,
	intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net] ice: Add more usage of existing function ice_get_vf_vsi(vf)
Date: Wed, 16 Nov 2022 17:39:41 +0100	[thread overview]
Message-ID: <Y3USTWD4GKx7ynkW@boxer> (raw)
In-Reply-To: <20221116044756.1021102-1-kalyan.kodamagula@intel.com>

On Tue, Nov 15, 2022 at 11:47:56PM -0500, Kalyan Kodamagula wrote:
> From: Brett Creeley <brett.creeley@intel.com>
> 
> Extend the usage of function ice_get_vf_vsi(vf)
> in multiple places instead of VF's VSI by using a long string
> of dereferences (i.e. vf->pf->vsi[vf->lan_vsi_idx]).
> 
> Fixes: c5afbe99b778c ("ice: Add helper function to get the VF's VSIq")

I don't think it's a fix and a net candidate. Also seems date on your
machine is off, some people on this list might yell at you for this :P

> Signed-off-by: Brett Creeley <brett.creeley@intel.com>
> Signed-off-by: Kalyan Kodamagula <kalyan.kodamagula@intel.com>
> ---
>  drivers/net/ethernet/intel/ice/ice_virtchnl_fdir.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/ethernet/intel/ice/ice_virtchnl_fdir.c b/drivers/net/ethernet/intel/ice/ice_virtchnl_fdir.c
> index c6a58343d81d..e6ef6b303222 100644
> --- a/drivers/net/ethernet/intel/ice/ice_virtchnl_fdir.c
> +++ b/drivers/net/ethernet/intel/ice/ice_virtchnl_fdir.c
> @@ -113,7 +113,7 @@ ice_vc_fdir_param_check(struct ice_vf *vf, u16 vsi_id)
>  	if (!ice_vc_isvalid_vsi_id(vf, vsi_id))
>  		return -EINVAL;
>  
> -	if (!pf->vsi[vf->lan_vsi_idx])
> +	if (!ice_get_vf_vsi(vf))
>  		return -EINVAL;
>  
>  	return 0;
> @@ -494,7 +494,7 @@ ice_vc_fdir_rem_prof(struct ice_vf *vf, enum ice_fltr_ptype flow, int tun)
>  
>  	vf_prof = fdir->fdir_prof[flow];
>  
> -	vf_vsi = pf->vsi[vf->lan_vsi_idx];
> +	vf_vsi = ice_get_vf_vsi(vf);
>  	if (!vf_vsi) {
>  		dev_dbg(dev, "NULL vf %d vsi pointer\n", vf->vf_id);
>  		return;
> @@ -572,7 +572,7 @@ ice_vc_fdir_write_flow_prof(struct ice_vf *vf, enum ice_fltr_ptype flow,
>  	pf = vf->pf;
>  	dev = ice_pf_to_dev(pf);
>  	hw = &pf->hw;
> -	vf_vsi = pf->vsi[vf->lan_vsi_idx];
> +	vf_vsi = ice_get_vf_vsi(vf);
>  	if (!vf_vsi)
>  		return -EINVAL;
>  
> @@ -1205,7 +1205,7 @@ static int ice_vc_fdir_write_fltr(struct ice_vf *vf,
>  	pf = vf->pf;
>  	dev = ice_pf_to_dev(pf);
>  	hw = &pf->hw;
> -	vsi = pf->vsi[vf->lan_vsi_idx];
> +	vsi = ice_get_vf_vsi(vf);
>  	if (!vsi) {
>  		dev_dbg(dev, "Invalid vsi for VF %d\n", vf->vf_id);
>  		return -EINVAL;
> -- 
> 2.38.1
> 
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      reply	other threads:[~2022-11-16 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  4:47 [Intel-wired-lan] [PATCH net] ice: Add more usage of existing function ice_get_vf_vsi(vf) Kalyan Kodamagula
2022-11-16 16:39 ` Maciej Fijalkowski [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=Y3USTWD4GKx7ynkW@boxer \
    --to=maciej.fijalkowski@intel.com \
    --cc=brett.creeley@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kalyan.kodamagula@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