> -----Original Message-----
> From: Lobakin, Aleksander <aleksander.lobakin@intel.com>
> Sent: Wednesday, April 16, 2025 8:49 AM
> To: Zaremba, Larysa <larysa.zaremba@intel.com>
> Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L
> <anthony.l.nguyen@intel.com>; David S. Miller <davem@davemloft.net>;
> Dumazet, Eric <edumazet@google.com>; Jakub Kicinski <kuba@kernel.org>;
> Paolo Abeni <pabeni@redhat.com>; Simon Horman <horms@kernel.org>;
> Jonathan Corbet <corbet@lwn.net>; Kitszel, Przemyslaw
> <przemyslaw.kitszel@intel.com>; Jiri Pirko <jiri@resnulli.us>; Mustafa Ismail
> <mustafa.ismail@intel.com>; Nikolova, Tatyana E
> <tatyana.e.nikolova@intel.com>; Andrew Lunn <andrew+netdev@lunn.ch>;
> Michael Ellerman <mpe@ellerman.id.au>; Fijalkowski, Maciej
> <maciej.fijalkowski@intel.com>; Lee Trager <lee@trager.us>; Madhavan
> Srinivasan <maddy@linux.ibm.com>; Samudrala, Sridhar
> <sridhar.samudrala@intel.com>; Keller, Jacob E <jacob.e.keller@intel.com>;
> Michal Swiatkowski <michal.swiatkowski@linux.intel.com>; Polchlopek, Mateusz
> <mateusz.polchlopek@intel.com>; Wenjun Wu <wenjun1.wu@intel.com>; Zaki,
> Ahmed <ahmed.zaki@intel.com>; netdev@vger.kernel.org; linux-
> doc@vger.kernel.org; linux-kernel@vger.kernel.org; Karlsson, Magnus
> <magnus.karlsson@intel.com>; Tantilov, Emil S <emil.s.tantilov@intel.com>;
> Chittim, Madhu <madhu.chittim@intel.com>; Hay, Joshua A
> <joshua.a.hay@intel.com>; Olech, Milena <milena.olech@intel.com>; Linga,
> Pavan Kumar <pavan.kumar.linga@intel.com>; Singhai, Anjali
> <anjali.singhai@intel.com>
> Subject: Re: [PATCH iwl-next 00/14] Introduce iXD driver
> 
> From: Larysa Zaremba <larysa.zaremba@intel.com>
> Date: Tue, 8 Apr 2025 14:47:46 +0200
> 
> > This patch series adds the iXD driver, which supports the Intel(R)
> > Control Plane PCI Function on Intel E2100 and later IPUs and FNICs.
> > It facilitates a centralized control over multiple IDPF PFs/VFs/SFs
> > exposed by the same card. The reason for the separation is to be able
> > to offload the control plane to the host different from where the data
> > plane is running.
> 
> BTW please move everything you're adding to libeth to libie instead.
> This PCI/VC/CP functionality is unlikely to be used by other vendors.
> Since libie_cp.ko or how you may want to call it won't link with base
> libie.ko, it won't have any pre-idpf HW-specific symbols, so that idpf
> could link with it.
> libeth stuff is purely vendor-agnostic and I'd really like to keep it so.
> 
> Thanks,
> Olek

I agree with this too.

Thanks,
Jake