netdev - Re: [PATCH net-next] pcnet32: remove VLB support

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: <alpine.DEB.2.21.2601152121230.6421@angie.orcam.me.uk>
Date: Thu, 15 Jan 2026 21:28:10 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Simon Horman <horms@...nel.org>
cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>, 
    Ethan Nelson-Moore <enelsonmoore@...il.com>, linux-mips@...r.kernel.org, 
    netdev@...r.kernel.org
Subject: Re: [PATCH net-next] pcnet32: remove VLB support

On Thu, 15 Jan 2026, Simon Horman wrote:

> >  No attention means the driver just works, why wouldn't it?  It's no 
> > rocket science.  FWIW I continue using several drivers that saw little to 
> > no change recently across various platforms.
> 
> Interesting. Subjectively, I'd say that Networking drivers it can be a sign
> that the devices aren't being used in the wild. But clearly that signal was
> incorrect in this case.

 A stable driver usually doesn't require attention.  A potential issue is 
using dangerous C language features or ones that have been obsoleted in a 
newer version of the standard, which cause compilation warnings or errors 
in a new version of the compiler.  But that depends on how a given driver 
was written in the first place.

  Maciej