Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Ahmed Zaki <ahmed.zaki@intel.com>, <intel-wired-lan@lists.osuosl.org>
Cc: Haiyue Wang <haiyue.wang@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 3/4] ice: Fix VLAN and CRC strip co-existence
Date: Thu, 31 Aug 2023 13:33:12 -0700	[thread overview]
Message-ID: <ddab394e-438d-bc77-8018-08ed8406ec43@intel.com> (raw)
In-Reply-To: <20230830214821.3439959-4-ahmed.zaki@intel.com>



On 8/30/2023 2:48 PM, Ahmed Zaki wrote:
> From: Haiyue Wang <haiyue.wang@intel.com>

...

> @@ -2673,10 +2696,15 @@ static int ice_vf_init_vlan_stripping(struct ice_vf *vf)
>   	if (ice_vf_is_port_vlan_ena(vf) && !ice_is_dvm_ena(&vsi->back->hw))
>   		return 0;
>   
> -	if (ice_vf_vlan_offload_ena(vf->driver_caps))
> -		return vsi->inner_vlan_ops.ena_stripping(vsi, ETH_P_8021Q);
> -	else
> -		return vsi->inner_vlan_ops.dis_stripping(vsi);
> +	if (ice_vf_vlan_offload_ena(vf->driver_caps)) {
> +		int err = vsi->inner_vlan_ops.ena_stripping(vsi,
> +							    ETH_P_8021Q);
> +		if (!err)
> +			vf->vlan_strip_ena |= ICE_INNER_VLAN_STRIP_ENA;

Need a newline separator for declarations. This supersedes the no 
newline between function call and error check. However, since your 
declaration line wraps, it would be preferred to do this:

		int err;

		err = vsi->inner_vlan_ops.ena_stripping(vsi, ETH_P_8021Q);
		if (!err)
			...

which should resolve all the issues.


> +		return err;
> +	}
> +

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-08-31 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 21:48 [Intel-wired-lan] [PATCH iwl-next v2 0/4] Support rx-fcs on/off for VFs Ahmed Zaki
2023-08-30 21:48 ` [Intel-wired-lan] [PATCH iwl-next v2 1/4] virtchnl: Add CRC stripping capability Ahmed Zaki
2023-08-30 21:48 ` [Intel-wired-lan] [PATCH iwl-next v2 2/4] ice: Support FCS/CRC strip disable for VF Ahmed Zaki
2023-08-30 21:48 ` [Intel-wired-lan] [PATCH iwl-next v2 3/4] ice: Fix VLAN and CRC strip co-existence Ahmed Zaki
2023-08-31 20:33   ` Tony Nguyen [this message]
2023-08-30 21:48 ` [Intel-wired-lan] [PATCH iwl-next v2 4/4] iavf: Add ability to turn off CRC stripping for VF Ahmed Zaki

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=ddab394e-438d-bc77-8018-08ed8406ec43@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=ahmed.zaki@intel.com \
    --cc=haiyue.wang@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@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