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: <3477f7ca-2ba8-48db-3086-481c0d35e83f@amd.com> Date: Tue, 4 Apr 2023 09:25:50 -0700 From: Shannon Nelson <shannon.nelson@....com> To: "Orr, Michael" <michael.orr@...el.com> Cc: Jakub Kicinski <kuba@...nel.org>, "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 On 4/4/23 12:59 AM, Orr, Michael wrote: > > This version is not yet the standard IDPF version. It is the current Intel driver. > The mentions of “standard” and OASIS Zaretsky because this version is the > Basis from which a standard driver WILL be developed at OASIS, which is relevant info to know. Please clearly spell out this intent and any related expectations in the cover letter. sln > > -- > Michael Orr. Cell: +1(408)636-3744 > Note: Dyslexic here. Even on speller-equipped iPad, typos Probable. > >> On Apr 4, 2023, at 01:55, Shannon Nelson <shannon.nelson@....com> wrote: >> >> On 4/3/23 3:20 PM, Jakub Kicinski wrote: >>> 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? >>> The noise about this driver being "a standard" is quite confusing. >>> 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 :( >> >> Just that they seem to be pushing it to become a standard through OASIS, >> as they infer by pointing to their OASIS docs in this patch, and I was under the (mistaken?) impression that this would be the One Driver for any device that implemented the HW/FW interface, kinda like virtio. If that's true, then why would the driver live under the Intel directory? >> >> sln
Powered by blists - more mailing lists