From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Michal Wilczynski <michal.wilczynski@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next v1 1/2] ice: Introduce enabling promiscuous mode on multiple VF's
Date: Tue, 28 Jun 2022 15:06:23 -0700 [thread overview]
Message-ID: <a45f2a0f-9aa5-1a81-42d5-c7e89e92398a@intel.com> (raw)
In-Reply-To: <20220624101611.1007933-2-michal.wilczynski@intel.com>
On 6/24/2022 3:16 AM, Michal Wilczynski wrote:
...
> @@ -3695,79 +3696,63 @@ bool ice_is_vsi_dflt_vsi(struct ice_sw *sw, struct ice_vsi *vsi)
> * Otherwise try to set the VSI passed in as the switch's default VSI and
> * return the result.
> */
> -int ice_set_dflt_vsi(struct ice_sw *sw, struct ice_vsi *vsi)
> +int ice_set_dflt_vsi(struct ice_vsi *vsi)
drivers/net/ethernet/intel/ice/ice_lib.c:3733: warning: Excess function
parameter 'sw' description in 'ice_set_dflt_vsi'
> {
> struct device *dev;
> int status;
>
...
> diff --git a/drivers/net/ethernet/intel/ice/ice_switch.c b/drivers/net/ethernet/intel/ice/ice_switch.c
> index 8d8f3eec79ee..f6cd73e9d451 100644
> --- a/drivers/net/ethernet/intel/ice/ice_switch.c
> +++ b/drivers/net/ethernet/intel/ice/ice_switch.c
> @@ -1298,6 +1298,9 @@ static DECLARE_BITMAP(recipe_to_profile[ICE_MAX_NUM_RECIPES],
> static DECLARE_BITMAP(profile_to_recipe[ICE_MAX_NUM_PROFILES],
> ICE_MAX_NUM_RECIPES);
>
> +static bool
> +ice_vsi_uses_fltr(struct ice_fltr_mgmt_list_entry *fm_entry, u16 vsi_handle);
> +
It looks like the function can be moved up to avoid the forward declaration.
> /**
> * ice_init_def_sw_recp - initialize the recipe book keeping tables
> * @hw: pointer to the HW struct
...
> @@ -3882,54 +3878,66 @@ int ice_cfg_dflt_vsi(struct ice_hw *hw, u16 vsi_handle, bool set, u8 direction)
> f_info.flag = direction;
> f_info.fltr_act = ICE_FWD_TO_VSI;
> f_info.fwd_id.hw_vsi_id = hw_vsi_id;
> + f_info.vsi_handle = vsi_handle;
>
> if (f_info.flag & ICE_FLTR_RX) {
> f_info.src = hw->port_info->lport;
> f_info.src_id = ICE_SRC_ID_LPORT;
> - if (!set)
> - f_info.fltr_rule_id =
> - hw->port_info->dflt_rx_vsi_rule_id;
> +
Odd place for newline
> } else if (f_info.flag & ICE_FLTR_TX) {
> f_info.src_id = ICE_SRC_ID_VSI;
> f_info.src = hw_vsi_id;
> - if (!set)
> - f_info.fltr_rule_id =
> - hw->port_info->dflt_tx_vsi_rule_id;
...
> +/**
> + * ice_check_if_dflt_vsi - check if VSI is default VSI
> + * @pi: pointer to the port_info structure
> + * @vsi_handle: vsi handle to check for in filter list
> + * @rule_exists: indicates if there are any VSI's in the rule list
> + *
> + * checks if the VSI is in a default VSI list, and also indicates
> + * if the default VSI list is empty
> + */
> +bool ice_check_if_dflt_vsi(struct ice_port_info *pi, u16 vsi_handle,
> + bool *rule_exists)
ice driver uses GNU style for multiline function declarations (same
comment for patch 2 as well)
e.g.
bool
ice_check_if_dflt_vsi(struct ice_port_info *pi...
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-06-28 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 10:16 [Intel-wired-lan] [PATCH net-next v1 0/2] Improvements for default VSI filter handling Michal Wilczynski
2022-06-24 10:16 ` [Intel-wired-lan] [PATCH net-next v1 1/2] ice: Introduce enabling promiscuous mode on multiple VF's Michal Wilczynski
2022-06-28 22:06 ` Tony Nguyen [this message]
2022-07-01 15:21 ` Wilczynski, Michal
2022-06-24 10:16 ` [Intel-wired-lan] [PATCH net-next v1 2/2] ice: Fix promiscuous mode not turning off Michal Wilczynski
2022-06-28 22:09 ` Tony Nguyen
2022-07-01 15:20 ` Wilczynski, Michal
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=a45f2a0f-9aa5-1a81-42d5-c7e89e92398a@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=michal.wilczynski@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