From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Simon Horman <horms@kernel.org>
Cc: Jacob Keller <jacob.e.keller@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
"Jiri Pirko" <jiri@resnulli.us>,
Tatyana Nikolova <tatyana.e.nikolova@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"Maciej Fijalkowski" <maciej.fijalkowski@intel.com>,
Lee Trager <lee@trager.us>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
Ahmed Zaki <ahmed.zaki@intel.com>, <netdev@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
Emil Tantilov <emil.s.tantilov@intel.com>,
"Madhu Chittim" <madhu.chittim@intel.com>,
Josh Hay <joshua.a.hay@intel.com>,
"Milena Olech" <milena.olech@intel.com>,
<pavan.kumar.linga@intel.com>,
"Singhai, Anjali" <anjali.singhai@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 01/14] virtchnl: create 'include/linux/intel' and move necessary header files
Date: Mon, 5 May 2025 09:56:37 +0200 [thread overview]
Message-ID: <aBhvNfWP-Rmec3Ci@soc-5CG4396X81.clients.intel.com> (raw)
In-Reply-To: <20250430085545.GT3339421@horms.kernel.org>
On Wed, Apr 30, 2025 at 09:55:45AM +0100, Simon Horman wrote:
> On Tue, Apr 29, 2025 at 11:47:58AM -0700, Jacob Keller wrote:
> >
> >
> > On 4/28/2025 9:15 AM, Simon Horman wrote:
> > > On Thu, Apr 24, 2025 at 01:32:24PM +0200, Larysa Zaremba wrote:
> > >> From: Victor Raj <victor.raj@intel.com>
> > >>
> > >> Move intel specific header files into new folder
> > >> include/linux/intel.
> > >>
> > >> Suggested-by: Alexander Lobakin <aleksander.lobakin@intel.com>
> > >> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> > >> Signed-off-by: Victor Raj <victor.raj@intel.com>
> > >> Signed-off-by: Larysa Zaremba <larysa.zaremba@intel.com>
> > >> ---
> > >> MAINTAINERS | 6 +++---
> > >> drivers/infiniband/hw/irdma/i40iw_if.c | 2 +-
> > >> drivers/infiniband/hw/irdma/main.h | 2 +-
> > >> drivers/infiniband/hw/irdma/osdep.h | 2 +-
> > >> drivers/net/ethernet/intel/i40e/i40e.h | 4 ++--
> > >> drivers/net/ethernet/intel/i40e/i40e_client.c | 2 +-
> > >> drivers/net/ethernet/intel/i40e/i40e_common.c | 2 +-
> > >> drivers/net/ethernet/intel/i40e/i40e_prototype.h | 2 +-
> > >> drivers/net/ethernet/intel/i40e/i40e_txrx.c | 2 +-
> > >> drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h | 2 +-
> > >> drivers/net/ethernet/intel/iavf/iavf.h | 2 +-
> > >> drivers/net/ethernet/intel/iavf/iavf_common.c | 2 +-
> > >> drivers/net/ethernet/intel/iavf/iavf_main.c | 2 +-
> > >> drivers/net/ethernet/intel/iavf/iavf_prototype.h | 2 +-
> > >> drivers/net/ethernet/intel/iavf/iavf_txrx.c | 2 +-
> > >> drivers/net/ethernet/intel/iavf/iavf_types.h | 4 +---
> > >> drivers/net/ethernet/intel/iavf/iavf_virtchnl.c | 2 +-
> > >> drivers/net/ethernet/intel/ice/ice.h | 2 +-
> > >> drivers/net/ethernet/intel/ice/ice_common.h | 2 +-
> > >> drivers/net/ethernet/intel/ice/ice_idc_int.h | 2 +-
> > >> drivers/net/ethernet/intel/ice/ice_txrx_lib.c | 2 +-
> > >> drivers/net/ethernet/intel/ice/ice_vf_lib.h | 2 +-
> > >> drivers/net/ethernet/intel/ice/ice_virtchnl.h | 2 +-
> > >> drivers/net/ethernet/intel/idpf/idpf.h | 2 +-
> > >> drivers/net/ethernet/intel/idpf/idpf_txrx.h | 2 +-
> > >> drivers/net/ethernet/intel/libie/rx.c | 2 +-
> > >> include/linux/{net => }/intel/i40e_client.h | 0
> > >> include/linux/{net => }/intel/iidc.h | 0
> > >> include/linux/{net => }/intel/libie/rx.h | 0
> > >> include/linux/{avf => intel}/virtchnl.h | 0
> > >> .../ethernet/intel/idpf => include/linux/intel}/virtchnl2.h | 0
> > >> .../intel/idpf => include/linux/intel}/virtchnl2_lan_desc.h | 0
> > >> 32 files changed, 29 insertions(+), 31 deletions(-)
> > >> rename include/linux/{net => }/intel/i40e_client.h (100%)
> > >> rename include/linux/{net => }/intel/iidc.h (100%)
> > >> rename include/linux/{net => }/intel/libie/rx.h (100%)
> > >> rename include/linux/{avf => intel}/virtchnl.h (100%)
> > >> rename {drivers/net/ethernet/intel/idpf => include/linux/intel}/virtchnl2.h (100%)
> > >> rename {drivers/net/ethernet/intel/idpf => include/linux/intel}/virtchnl2_lan_desc.h (100%)
> > >>
> > >> diff --git a/MAINTAINERS b/MAINTAINERS
> > >> index 657a67f9031e..2e2a57dfea8f 100644
> > >> --- a/MAINTAINERS
> > >> +++ b/MAINTAINERS
> > >> @@ -11884,8 +11884,8 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git
> > >> F: Documentation/networking/device_drivers/ethernet/intel/
> > >> F: drivers/net/ethernet/intel/
> > >> F: drivers/net/ethernet/intel/*/
> > >> -F: include/linux/avf/virtchnl.h
> > >> -F: include/linux/net/intel/iidc.h
> > >> +F: include/linux/intel/iidc.h
> > >> +F: include/linux/intel/virtchnl.h
> > >
> > > I'm not sure that I understand the motivation for moving files out of
> > > include/linux/net, but I guess the answer is that my suggestion, which
> > > would be to move files into include/linux/net, is somehow less good.
> > >
> > > But if file are moving out of include/linux/net then I think it would
> > > make sense to make a corresponding update to NETWORKING DRIVERS.
> > >
> > > Also, include/linux/intel, does feel a bit too general. These files
> > > seem to relate to NICs (of some sort of flavour or another). But Intel
> > > does a lot more than make NICs.
> > >
> >
> > 'include/linux/net/intel' seems fine to me. I agree with moving
> > virtchnl.h there since it is quite clear that any historical ambitions
> > about AVF being vendor agnostic are long dead, so having it in its own
> > 'non-intel' folder is silly.
> >
> > Strictly speaking, I think the goal of moving the files is due to the
> > fact that a lot of the core ixd code is not really network layer but
> > instead PCI layer.
>
> Sure. I was more thinking out loud in my previous email than requesting any
> action. Thanks for filling in my understanding of the situation.
>
Olek suggested this because intel was the only resident in include/linux/net and
include/linux/intel was vacant.
> But could we please consider updating NETWORKING DRIVERS so
> that get_maintainers.pl can help people to CC netdev and it's maintainers
> as appropriate?
I am not sure what kind of update do you mean, include/linux/net directory was
not under any maintainer. include/linux/mlx5 and include/linux/mlx4 are only
under vendor maintainers.
For sure I should add include/linux/intel/* under Tony.
Do you think it also should be added to general networking maintainers?
next prev parent reply other threads:[~2025-05-05 7:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 11:32 [PATCH iwl-next v2 00/14] Introduce iXD driver Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 01/14] virtchnl: create 'include/linux/intel' and move necessary header files Larysa Zaremba
2025-04-28 16:15 ` Simon Horman
2025-04-29 18:47 ` [Intel-wired-lan] " Jacob Keller
2025-04-30 8:55 ` Simon Horman
2025-05-05 7:56 ` Larysa Zaremba [this message]
2025-05-06 15:59 ` Simon Horman
2025-05-07 7:13 ` Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 02/14] virtchnl: introduce control plane version fields Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 03/14] libie: add PCI device initialization helpers to libie Larysa Zaremba
2025-04-28 16:56 ` Simon Horman
2025-05-05 6:56 ` Larysa Zaremba
2025-05-06 15:56 ` Simon Horman
2025-04-24 11:32 ` [PATCH iwl-next v2 04/14] libeth: allow to create fill queues without NAPI Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 05/14] libie: add control queue support Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 06/14] libie: add bookkeeping support for control queue messages Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 07/14] idpf: remove 'vport_params_reqd' field Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 08/14] idpf: refactor idpf to use libie controlq and Xn APIs Larysa Zaremba
2025-04-24 15:32 ` [Intel-wired-lan] " Paul Menzel
2025-04-24 15:37 ` Keller, Jacob E
2025-04-25 10:22 ` Larysa Zaremba
2025-04-25 10:11 ` Larysa Zaremba
2025-04-25 10:30 ` Paul Menzel
2025-04-28 18:03 ` Simon Horman
2025-05-05 7:09 ` Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 09/14] idpf: make mbx_task queueing and cancelling more consistent Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 10/14] idpf: print a debug message and bail in case of non-event ctlq message Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 11/14] ixd: add basic driver framework for Intel(R) Control Plane Function Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 12/14] ixd: add reset checks and initialize the mailbox Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 13/14] ixd: add the core initialization Larysa Zaremba
2025-04-24 11:32 ` [PATCH iwl-next v2 14/14] ixd: add devlink support Larysa Zaremba
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=aBhvNfWP-Rmec3Ci@soc-5CG4396X81.clients.intel.com \
--to=larysa.zaremba@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anjali.singhai@intel.com \
--cc=anthony.l.nguyen@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=jiri@resnulli.us \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=maddy@linux.ibm.com \
--cc=madhu.chittim@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=milena.olech@intel.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.kumar.linga@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=tatyana.e.nikolova@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).