From: Simon Horman <horms@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
hkelam@marvell.com, Junfeng Guo <junfeng.guo@intel.com>,
Marcin Szycik <marcin.szycik@linux.intel.com>,
Rafal Romanowski <rafal.romanowski@intel.com>
Subject: Re: [PATCH iwl-next v5 10/13] ice: add method to disable FDIR SWAP option
Date: Tue, 30 Jul 2024 11:23:39 +0100 [thread overview]
Message-ID: <20240730102339.GW97837@kernel.org> (raw)
In-Reply-To: <20240725220810.12748-11-ahmed.zaki@intel.com>
On Thu, Jul 25, 2024 at 04:08:06PM -0600, Ahmed Zaki wrote:
> From: Junfeng Guo <junfeng.guo@intel.com>
>
> The SWAP Flag in the FDIR Programming Descriptor doesn't work properly,
> it is always set and cannot be unset (hardware bug). Thus, add a method
> to effectively disable the FDIR SWAP option by setting the FDSWAP instead
> of FDINSET registers.
>
> Reviewed-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>
> Tested-by: Rafal Romanowski <rafal.romanowski@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-07-30 10:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 22:07 [PATCH iwl-next v5 00/13] ice: iavf: add support for TC U32 filters on VFs Ahmed Zaki
2024-07-25 22:07 ` [PATCH iwl-next v5 01/13] ice: add parser create and destroy skeleton Ahmed Zaki
2024-07-25 22:07 ` [PATCH iwl-next v5 02/13] ice: parse and init various DDP parser sections Ahmed Zaki
2024-07-30 10:22 ` Simon Horman
2024-07-25 22:07 ` [PATCH iwl-next v5 03/13] ice: add debugging functions for the " Ahmed Zaki
2024-07-25 22:08 ` [PATCH iwl-next v5 04/13] ice: add parser internal helper functions Ahmed Zaki
2024-07-25 22:08 ` [PATCH iwl-next v5 05/13] ice: add parser execution main loop Ahmed Zaki
2024-07-30 10:22 ` Simon Horman
2024-07-25 22:08 ` [PATCH iwl-next v5 06/13] ice: support turning on/off the parser's double vlan mode Ahmed Zaki
2024-07-30 10:23 ` Simon Horman
2024-07-25 22:08 ` [PATCH iwl-next v5 07/13] ice: add UDP tunnels support to the parser Ahmed Zaki
2024-07-25 22:08 ` [PATCH iwl-next v5 08/13] ice: add API for parser profile initialization Ahmed Zaki
2024-07-30 10:23 ` Simon Horman
2024-07-25 22:08 ` [PATCH iwl-next v5 09/13] virtchnl: support raw packet in protocol header Ahmed Zaki
2024-07-25 22:08 ` [PATCH iwl-next v5 10/13] ice: add method to disable FDIR SWAP option Ahmed Zaki
2024-07-30 10:23 ` Simon Horman [this message]
2024-07-25 22:08 ` [PATCH iwl-next v5 11/13] ice: enable FDIR filters from raw binary patterns for VFs Ahmed Zaki
2024-07-30 10:28 ` Simon Horman
2024-07-25 22:08 ` [PATCH iwl-next v5 12/13] iavf: refactor add/del FDIR filters Ahmed Zaki
2024-07-30 10:28 ` Simon Horman
2024-07-25 22:08 ` [PATCH iwl-next v5 13/13] iavf: add support for offloading tc U32 cls filters Ahmed Zaki
2024-07-30 10:29 ` Simon Horman
2024-07-25 22:26 ` [PATCH iwl-next v5 00/13] ice: iavf: add support for TC U32 filters on VFs Jakub Kicinski
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=20240730102339.GW97837@kernel.org \
--to=horms@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=hkelam@marvell.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=junfeng.guo@intel.com \
--cc=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=rafal.romanowski@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;
as well as URLs for NNTP newsgroup(s).