> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-boun...@osuosl.org> On Behalf Of
> Jedrzej Jagielski
> Sent: Friday, February 21, 2025 5:21 PM
> To: intel-wired-...@lists.osuosl.org
> Cc: Nguyen, Anthony L <anthony.l.ngu...@intel.com>;
> net...@vger.kernel.org; ho...@kernel.org; j...@nvidia.com; Jagielski, Jedrzej
> <jedrzej.jagiel...@intel.com>; Polchlopek, Mateusz
> <mateusz.polchlo...@intel.com>; Kitszel, Przemyslaw
> <przemyslaw.kits...@intel.com>
> Subject: [Intel-wired-lan] [PATCH iwl-next v5 03/15] ixgbe: add initial 
> devlink
> support
> 
> Add an initial support for devlink interface to ixgbe driver.
> 
> Similarly to i40e driver the implementation doesn't enable devlink to manage
> device-wide configuration. Devlink instance is created for each physical
> function of PCIe device.
> 
> Create separate directory for devlink related ixgbe files and use naming 
> scheme
> similar to the one used in the ice driver.
> 
> Add a stub for Documentation, to be extended by further patches.
> 
> Change struct ixgbe_adapter allocation to be done by devlink (Przemek), as
> suggested by Jiri.
> 
> Reviewed-by: Mateusz Polchlopek <mateusz.polchlo...@intel.com>
> Co-developed-by: Przemek Kitszel <przemyslaw.kits...@intel.com>
> Signed-off-by: Przemek Kitszel <przemyslaw.kits...@intel.com>
> Signed-off-by: Jedrzej Jagielski <jedrzej.jagiel...@intel.com>
> ---
> v2: fix error patch in probe; minor tweaks
> v4: alloc ixgbe_adapter by devlink
> ---
>  Documentation/networking/devlink/index.rst    |  1 +
>  Documentation/networking/devlink/ixgbe.rst    |  8 ++
>  drivers/net/ethernet/intel/Kconfig            |  1 +
>  drivers/net/ethernet/intel/ixgbe/Makefile     |  3 +-
>  .../ethernet/intel/ixgbe/devlink/devlink.c    | 77 +++++++++++++++++++
>  .../ethernet/intel/ixgbe/devlink/devlink.h    | 10 +++
>  drivers/net/ethernet/intel/ixgbe/ixgbe.h      | 12 ++-
>  drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 30 +++++++-
>  8 files changed, 138 insertions(+), 4 deletions(-)  create mode 100644
> 

Tested-by: Bharath R <bharat...@intel.com>

Reply via email to