| 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: <20240410130344.11292750@kernel.org> Date: Wed, 10 Apr 2024 13:03:44 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Florian Fainelli <f.fainelli@...il.com> Cc: Jiri Pirko <jiri@...nulli.us>, pabeni@...hat.com, John Fastabend <john.fastabend@...il.com>, Alexander Lobakin <aleksander.lobakin@...el.com>, Andrew Lunn <andrew@...n.ch>, Daniel Borkmann <daniel@...earbox.net>, Edward Cree <ecree.xilinx@...il.com>, Alexander Duyck <alexander.duyck@...il.com>, netdev@...r.kernel.org, bhelgaas@...gle.com, linux-pci@...r.kernel.org, Alexander Duyck <alexanderduyck@...com>, Willem de Bruijn <willemdebruijn.kernel@...il.com> Subject: Re: [net-next PATCH 00/15] eth: fbnic: Add network driver for Meta Platforms Host Network Interface On Wed, 10 Apr 2024 11:00:35 -0700 Florian Fainelli wrote: > although I cannot really think about an "implied" metric that we could > track, short of monitoring patches/bug reports coming from outside of > the original driver authors/owners as an indication of how widely > utilized a given driver is. Not metric, just to clarify. I think the discussion started from my email saying: - help with refactoring / adapting their drivers more actively and that may be an empty promise if the person doing the refactoring does not know they could ask. It's not uncommon for a relative newcomer to redo some internal API. Not that it's usually a hard transformation.. Dunno, a bit hypothetical.
Powered by blists - more mailing lists