netdev - Re: [Intel-wired-lan] [PATCH net-next 00/15] Introduce IDPF driver

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <703e473e-87f2-72af-1110-79f23f290a54@amd.com>
Date:   Fri, 7 Apr 2023 11:01:47 -0700
From:   Shannon Nelson <shannon.nelson@....com>
To:     Christoph Hellwig <hch@....de>,
        "Samudrala, Sridhar" <sridhar.samudrala@...el.com>
Cc:     Jason Gunthorpe <jgg@...dia.com>, Jakub Kicinski <kuba@...nel.org>,
        Pavan Kumar Linga <pavan.kumar.linga@...el.com>,
        intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
        shiraz.saleem@...el.com, emil.s.tantilov@...el.com,
        willemb@...gle.com, decot@...gle.com, joshua.a.hay@...el.com,
        michael.orr@...el.com, anjali.singhai@...el.com
Subject: Re: [Intel-wired-lan] [PATCH net-next 00/15] Introduce IDPF driver

On 4/6/23 9:39 PM, Christoph Hellwig wrote:
> 
> FYI, thanks to Michael for the feedback.
> 
>> As explained in the Charter, Intel & Google are donating the current
>> Vendor driver & its spec to the IDPF TC to serve as a starting point for
>> an eventual vendor-agnostic Spec & Driver that will be the OASIS IDPF
>> standard set.
> 
> Having both under the same name seems like a massive confusion.

I was thinking something similar.  If "idpf" is likely to be the final 
generic driver name (which makes sense), and Intel's driver is an 
Intel-device specific driver, can Intel use a more Intel-device specific 
name for their driver?  This would help both in reminding us that this 
isn't intended as the vendor-agnostic driver, and would prevent 
potential future name confusion.

sln