Hi Ahmed,
kernel test robot noticed the following build errors:
[auto build test ERROR on tnguy-next-queue/dev-queue]
url:
https://github.com/intel-lab-lkp/linux/commits/Ahmed-Zaki/virtchnl2-add-flow-steering-support/20250324-215138
base: https://git.kernel.org/pub/scm/linux/kernel/git
Use the new virtchnl2 OP codes to communicate with the Control Plane to
add flow steering filters. We add the basic functionality for ADD/Delete
with TCP/UDP IPv4 only. Support for other OP codes and protocols will be
added later.
Reviewed-by: Sridhar Samudrala
Signed-off-by: Ahmed Zaki
---
dri
From: Sudheer Mogilappagari
Add opcodes and corresponding message structure to add and delete
flow steering rules. Flow steering enables configuration
of rules to take an action or subset of actions based on a match
criteria. Actions could be redirect to queue, redirect to queue
group, drop packe
Add basic flow steering. For now, we support IPv4 and TCP/UDP only.
Ahmed Zaki (1):
idpf: add flow steering support
Sudheer Mogilappagari (1):
virtchnl2: add flow steering support
drivers/net/ethernet/intel/idpf/idpf.h| 14 +
.../net/ethernet/intel/idpf/idpf_ethtool.c| 297
Hi Ahmed,
kernel test robot noticed the following build errors:
[auto build test ERROR on tnguy-next-queue/dev-queue]
url:
https://github.com/intel-lab-lkp/linux/commits/Ahmed-Zaki/virtchnl2-add-flow-steering-support/20250324-215138
base: https://git.kernel.org/pub/scm/linux/kernel/git
> -Original Message-
> From: Rinitha, SX
> Sent: Friday, March 21, 2025 5:47 AM
> To: Kyungwook Boo ; Loktionov, Aleksandr
> ; Kitszel, Przemyslaw
> ; Nguyen, Anthony L
>
> Cc: intel-wired-...@lists.osuosl.org; net...@vger.kernel.org
> Subject: RE: [Intel-wired-lan] [PATCH iwl-next v2]
On 22/02/2025 14:46, Piotr Wejman wrote:
Update the driver to use the new hardware timestamping API added in commit
66f7223039c0 ("net: add NDOs for configuring hardware timestamping").
Use Netlink extack for error reporting in e1000e_config_hwtstamp.
Align the indentation of net_device_ops.
On 3/21/25 10:52, luoxuanqiang wrote:
From: luoxuanqiang
As mentioned in the commit baeb705fd6a7 ("ice: always check VF VSI
pointer values"), we need to perform a null pointer check on the return
value of ice_get_vf_vsi() before using it.
Fixes: 6ebbe97a4881 ("ice: Add a per-VF limit on number
On 3/21/25 16:13, Michal Kubiak wrote:
The "ice" driver implementation uses the control VSI to handle
the flow director configuration for PFs and VFs.
Unfortunately, although a separate VSI type was created to handle flow
director queues, the Rx queue handler was shared between the flow
director
