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: <Yr7NpQz6/esZAiZv@nanopsycho>
Date:   Fri, 1 Jul 2022 12:34:13 +0200
From:   Jiri Pirko <jiri@...nulli.us>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
        pabeni@...hat.com, corbet@....net, jdmason@...zu.us,
        vburru@...vell.com, jiawenwu@...stnetic.com,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next] eth: remove neterion/vxge

Fri, Jul 01, 2022 at 06:42:34AM CEST, kuba@...nel.org wrote:
>The last meaningful change to this driver was made by Jon in 2011.
>As much as we'd like to believe that this is because the code is
>perfect the chances are nobody is using this hardware.

Hmm, I can understand what for driver for HW that is no longer
developed, the driver changes might be very minimal. The fact that the
code does not change for years does not mean that there are users of
this NIC which this patch would break :/

Isn't there some obsoletion scheme globally applied to kernel device
support? I would expect something like that.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ