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 v2 0/2] Improvements for default VSI filter handling
Date: Fri, 1 Jul 2022 14:01:40 -0700 [thread overview]
Message-ID: <04c3c622-29d9-b538-2ce3-2864a43ee5fa@intel.com> (raw)
In-Reply-To: <20220701151750.2441885-1-michal.wilczynski@intel.com>
On 7/1/2022 8:17 AM, Michal Wilczynski wrote:
> Currently when vf-true-promisc-support private flag is set to false, default VSI
> switch filter is used instead of a proper promiscuous one. Unfortunately flow for
> default VSI is a bit different, which leads to improper behavior like not being
> able to enable promisc mode on multiple VF's, or filter not being removed in
> 'trust off' flow.
>
> v2:
> - Changed net-next to net, since this can be treated as a bug fixes
I think I may have been unclear on my previous question regarding this.
Patch 1 looks like improvement for handling so net-next seems the right
target for it. Patch 2 seems like it's resolving a bug which is why I
was asking why that wasn't going to net.
Also, for future reference, if the patch is going to net, you need to
add a Fixes: tag [1] to the patch(es).
[1]
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
> Michal Wilczynski (2):
> ice: Introduce enabling promiscuous mode on multiple VF's
> v2:
> - Removed unnecessary parameter in function description
> - Removed unnecessary comments
> - Moved ice_vsi_uses_fltr function
> - Removed unnecessary blank lines
> - Changed commit message to utilize full 75 characters
>
> ice: Fix promiscuous mode not turning off
>
> drivers/net/ethernet/intel/ice/ice.h | 2 -
> drivers/net/ethernet/intel/ice/ice_eswitch.c | 8 +-
> drivers/net/ethernet/intel/ice/ice_ethtool.c | 2 +-
> drivers/net/ethernet/intel/ice/ice_lib.c | 67 ++++-----
> drivers/net/ethernet/intel/ice/ice_lib.h | 9 +-
> drivers/net/ethernet/intel/ice/ice_main.c | 14 +-
> drivers/net/ethernet/intel/ice/ice_switch.c | 135 +++++++++---------
> drivers/net/ethernet/intel/ice/ice_switch.h | 6 +-
> drivers/net/ethernet/intel/ice/ice_type.h | 4 -
> drivers/net/ethernet/intel/ice/ice_vf_lib.c | 89 +++++++++---
> drivers/net/ethernet/intel/ice/ice_vf_lib.h | 7 +-
> drivers/net/ethernet/intel/ice/ice_virtchnl.c | 51 +++----
> 12 files changed, 216 insertions(+), 178 deletions(-)
>
_______________________________________________
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-07-01 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 15:17 [Intel-wired-lan] [PATCH net v2 0/2] Improvements for default VSI filter handling Michal Wilczynski
2022-07-01 15:17 ` [Intel-wired-lan] [PATCH net v2 1/2] ice: Introduce enabling promiscuous mode on multiple VF's Michal Wilczynski
2022-07-01 15:17 ` [Intel-wired-lan] [PATCH net v2 2/2] ice: Fix promiscuous mode not turning off Michal Wilczynski
2022-07-01 21:01 ` Tony Nguyen [this message]
2022-07-04 11:23 ` [Intel-wired-lan] [PATCH net v2 0/2] Improvements for default VSI filter handling Wilczynski, Michal
2022-07-12 21:57 ` Tony Nguyen
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=04c3c622-29d9-b538-2ce3-2864a43ee5fa@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