public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larysa Zaremba <larysa.zaremba@intel.com>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>
Cc: "intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"Lobakin, Aleksander" <aleksander.lobakin@intel.com>,
	"Samudrala, Sridhar" <sridhar.samudrala@intel.com>,
	Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
	"Tantilov, Emil S" <emil.s.tantilov@intel.com>,
	"Chittim, Madhu" <madhu.chittim@intel.com>,
	"Hay, Joshua A" <joshua.a.hay@intel.com>,
	"Keller, Jacob E" <jacob.e.keller@intel.com>,
	"Shanmugam, Jayaprakash" <jayaprakash.shanmugam@intel.com>,
	Jiri Pirko <jiri@resnulli.us>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Richard Cochran <richardcochran@gmail.com>,
	"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"R, Bharath" <bharath.r@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v7 14/14] ixd: add devlink support
Date: Tue, 28 Apr 2026 16:13:49 +0200	[thread overview]
Message-ID: <afDAnbuQaZ2DhpFs@soc-5CG4396X81.clients.intel.com> (raw)
In-Reply-To: <IA3PR11MB8986407D74E9DE59F31B7AB5E5372@IA3PR11MB8986.namprd11.prod.outlook.com>

On Tue, Apr 28, 2026 at 10:53:47AM +0200, Loktionov, Aleksandr wrote:
> 
> 
> > -----Original Message-----
> > From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf
> > Of Larysa Zaremba
> > Sent: Tuesday, April 28, 2026 10:27 AM
> > To: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L
> > <anthony.l.nguyen@intel.com>
> > Cc: Lobakin, Aleksander <aleksander.lobakin@intel.com>; Samudrala,
> > Sridhar <sridhar.samudrala@intel.com>; Michal Swiatkowski
> > <michal.swiatkowski@linux.intel.com>; Zaremba, Larysa
> > <larysa.zaremba@intel.com>; Fijalkowski, Maciej
> > <maciej.fijalkowski@intel.com>; Tantilov, Emil S
> > <emil.s.tantilov@intel.com>; Chittim, Madhu <madhu.chittim@intel.com>;
> > Hay, Joshua A <joshua.a.hay@intel.com>; Keller, Jacob E
> > <jacob.e.keller@intel.com>; Shanmugam, Jayaprakash
> > <jayaprakash.shanmugam@intel.com>; Jiri Pirko <jiri@resnulli.us>;
> > David S. Miller <davem@davemloft.net>; Eric Dumazet
> > <edumazet@google.com>; Jakub Kicinski <kuba@kernel.org>; Paolo Abeni
> > <pabeni@redhat.com>; Simon Horman <horms@kernel.org>; Jonathan Corbet
> > <corbet@lwn.net>; Richard Cochran <richardcochran@gmail.com>; Kitszel,
> > Przemyslaw <przemyslaw.kitszel@intel.com>; Andrew Lunn
> > <andrew+netdev@lunn.ch>; netdev@vger.kernel.org; linux-
> > doc@vger.kernel.org; linux-kernel@vger.kernel.org; R, Bharath
> > <bharath.r@intel.com>
> > Subject: [Intel-wired-lan] [PATCH iwl-next v7 14/14] ixd: add devlink
> > support
> > 
> > From: Amritha Nambiar <amritha.nambiar@intel.com>
> > 
> > Enable initial support for the devlink interface with the ixd driver.
> > The ixd hardware is a single function PCIe device. So, the PCIe
> > adapter gets its own devlink instance to manage device-wide resources
> > or configuration.
> > 
> > $ devlink dev show
> > pci/0000:83:00.6
> > 
> > $ devlink dev info pci/0000:83:00.6
> > pci/0000:83:00.6:
> >   driver ixd
> >   serial_number 00-a0-c9-ff-ff-23-45-67
> >   versions:
> >       fixed:
> >         device.type MEV
> >       running:
> >         virtchnl 2.0
> > 
> > Signed-off-by: Amritha Nambiar <amritha.nambiar@intel.com>
> > Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> > Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> > Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> > Signed-off-by: Larysa Zaremba <larysa.zaremba@intel.com>
> > Tested-by: Bharath R <Bharath.r@intel.com>
> > Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> > ---
> >  Documentation/networking/devlink/index.rst   |  1 +
> >  Documentation/networking/devlink/ixd.rst     | 30 ++++++
> >  drivers/net/ethernet/intel/ixd/Kconfig       |  1 +
> >  drivers/net/ethernet/intel/ixd/Makefile      |  1 +
> >  drivers/net/ethernet/intel/ixd/ixd_devlink.c | 97
> > ++++++++++++++++++++  drivers/net/ethernet/intel/ixd/ixd_devlink.h |
> > 44 +++++++++
> >  drivers/net/ethernet/intel/ixd/ixd_main.c    | 16 +++-
> >  7 files changed, 187 insertions(+), 3 deletions(-)  create mode
> > 100644 Documentation/networking/devlink/ixd.rst
> >  create mode 100644 drivers/net/ethernet/intel/ixd/ixd_devlink.c
> >  create mode 100644 drivers/net/ethernet/intel/ixd/ixd_devlink.h
> > 
> > diff --git a/Documentation/networking/devlink/index.rst
> > b/Documentation/networking/devlink/index.rst
> > index f7ba7dcf477d..f0c077843fa7 100644
> > --- a/Documentation/networking/devlink/index.rst
> > +++ b/Documentation/networking/devlink/index.rst
> > @@ -88,6 +88,7 @@ parameters, info versions, and other features it
> > supports.
> >     ionic
> >     iosm
> >     ixgbe
> 
> ...
> 
> > --- /dev/null
> > +++ b/drivers/net/ethernet/intel/ixd/ixd_devlink.h
> > @@ -0,0 +1,44 @@
> > +/* SPDX-License-Identifier: GPL-2.0 */
> > +/* Copyright (c) 2025, Intel Corporation. */
> > +
> devlink.c  has:
> > +// SPDX-License-Identifier: GPL-2.0
> But devlink.h has:
> > +/* SPDX-License-Identifier: GPL-2.0 */
> 
> Why?

Because source and header files require different license format.

> 
> > +#ifndef _IXD_DEVLINK_H_
> > +#define _IXD_DEVLINK_H_
> > +#include <net/devlink.h>
> 
> ...
> 
> >  }
> > 
> >  static const struct pci_device_id ixd_pci_tbl[] = {
> > --
> > 2.47.0
> 

      reply	other threads:[~2026-04-28 14:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  8:26 [PATCH iwl-next v7 00/14] Introduce iXD driver Larysa Zaremba
2026-04-28  8:26 ` [PATCH iwl-next v7 01/14] virtchnl: create 'include/linux/intel' and move necessary header files Larysa Zaremba
2026-04-28 10:08   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28  8:26 ` [PATCH iwl-next v7 02/14] libie: add PCI device initialization helpers to libie Larysa Zaremba
2026-04-28 10:09   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28  8:26 ` [PATCH iwl-next v7 03/14] libeth: allow to create fill queues without NAPI Larysa Zaremba
2026-04-28  8:26 ` [PATCH iwl-next v7 04/14] libie: add control queue support Larysa Zaremba
2026-04-28 10:10   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28  8:26 ` [PATCH iwl-next v7 05/14] libie: add bookkeeping support for control queue messages Larysa Zaremba
2026-04-28 10:10   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28  8:26 ` [PATCH iwl-next v7 06/14] idpf: remove 'vport_params_reqd' field Larysa Zaremba
2026-04-28 10:10   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28  8:26 ` [PATCH iwl-next v7 07/14] idpf: refactor idpf to use libie_pci APIs Larysa Zaremba
2026-04-28  8:47   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 14:14     ` Larysa Zaremba
2026-04-28  9:00   ` Loktionov, Aleksandr
2026-04-28 14:16     ` Larysa Zaremba
2026-04-28  8:26 ` [PATCH iwl-next v7 08/14] idpf: refactor idpf to use libie control queues Larysa Zaremba
2026-04-28  8:26 ` [PATCH iwl-next v7 09/14] idpf: make mbx_task queueing and cancelling more consistent Larysa Zaremba
2026-04-28 10:11   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28  8:26 ` [PATCH iwl-next v7 10/14] idpf: print a debug message and bail in case of non-event ctlq message Larysa Zaremba
2026-04-28  8:26 ` [PATCH iwl-next v7 11/14] ixd: add basic driver framework for Intel(R) Control Plane Function Larysa Zaremba
2026-04-28 10:11   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28  8:26 ` [PATCH iwl-next v7 12/14] ixd: add reset checks and initialize the mailbox Larysa Zaremba
2026-04-28  8:26 ` [PATCH iwl-next v7 13/14] ixd: add the core initialization Larysa Zaremba
2026-04-28  8:50   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 14:12     ` Larysa Zaremba
2026-04-28  8:26 ` [PATCH iwl-next v7 14/14] ixd: add devlink support Larysa Zaremba
2026-04-28  8:53   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 14:13     ` Larysa Zaremba [this message]

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=afDAnbuQaZ2DhpFs@soc-5CG4396X81.clients.intel.com \
    --to=larysa.zaremba@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=bharath.r@intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=emil.s.tantilov@intel.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jayaprakash.shanmugam@intel.com \
    --cc=jiri@resnulli.us \
    --cc=joshua.a.hay@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=madhu.chittim@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=sridhar.samudrala@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