lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <DM8PR11MB5733BDA0029D6238A56686DAE9939@DM8PR11MB5733.namprd11.prod.outlook.com> Date: Tue, 4 Apr 2023 19:41:36 +0000 From: "Orr, Michael" <michael.orr@...el.com> To: Jakub Kicinski <kuba@...nel.org>, Shannon Nelson <shannon.nelson@....com> CC: "Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>, "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Saleem, Shiraz" <shiraz.saleem@...el.com>, "Tantilov, Emil S" <emil.s.tantilov@...el.com>, "willemb@...gle.com" <willemb@...gle.com>, "decot@...gle.com" <decot@...gle.com>, "Hay, Joshua A" <joshua.a.hay@...el.com>, "Samudrala, Sridhar" <sridhar.samudrala@...el.com>, "Brady, Alan" <alan.brady@...el.com>, "Chittim, Madhu" <madhu.chittim@...el.com>, "Burra, Phani R" <phani.r.burra@...el.com> Subject: RE: [Intel-wired-lan] [PATCH net-next 01/15] virtchnl: add virtchnl version 2 ops See below -----Original Message----- From: Jakub Kicinski <kuba@...nel.org> Sent: Tuesday, April 4, 2023 1:21 AM To: Shannon Nelson <shannon.nelson@....com> Cc: Linga, Pavan Kumar <pavan.kumar.linga@...el.com>; intel-wired-lan@...ts.osuosl.org; netdev@...r.kernel.org; Saleem, Shiraz <shiraz.saleem@...el.com>; Tantilov, Emil S <emil.s.tantilov@...el.com>; willemb@...gle.com; decot@...gle.com; Hay, Joshua A <joshua.a.hay@...el.com>; Samudrala, Sridhar <sridhar.samudrala@...el.com>; Brady, Alan <alan.brady@...el.com>; Chittim, Madhu <madhu.chittim@...el.com>; Burra, Phani R <phani.r.burra@...el.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.
Powered by blists - more mailing lists