[Intel-wired-lan] [PATCH net-next 01/15] virtchnl: add virtchnl version 2 ops

[Orr, Michael]

See below 

-----Original Message-----
From: Jakub Kicinski <kuba at kernel.org> 
Sent: Tuesday, April 4, 2023 1:21 AM
To: Shannon Nelson <shannon.nelson at amd.com>
Cc: Linga, Pavan Kumar <pavan.kumar.linga at intel.com>; intel-wired-lan at lists.osuosl.org; netdev at vger.kernel.org; Saleem, Shiraz <shiraz.saleem at intel.com>; Tantilov, Emil S <emil.s.tantilov at intel.com>; willemb at google.com; decot at google.com; Hay, Joshua A <joshua.a.hay at intel.com>; Samudrala, Sridhar <sridhar.samudrala at intel.com>; Brady, Alan <alan.brady at intel.com>; Chittim, Madhu <madhu.chittim at intel.com>; Burra, Phani R <phani.r.burra at intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next 01/15] virtchnl: add virtchnl version 2 ops

On Mon, 3 Apr 2023 15:01:55 -0700 Shannon Nelson wrote:
> > > diff --git a/drivers/net/ethernet/intel/idpf/virtchnl2.h 
> > > b/drivers/net/ethernet/intel/idpf/virtchnl2.h
> > 
> > If this is to be a standardized interface, why is this header buried 
> > in the driver specific directory instead of something more accessible 
> > like include/linux/idpf?

This is an Intel driver, hence in Intel tree location. When OASIS has a Standard driver,
(that will be based on, but different than this one) THAT driver will go where industry standard drivers belong. 


> The noise about this driver being "a standard" is quite confusing.

This driver is NOT "a standard". 

> Are you considering implementing any of it?

> I haven't heard of anyone who is yet, so I thought all this talk of a standard is pretty empty from the technical perspective :(

Agreed.