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]
Date:   Wed, 11 Jan 2017 09:05:02 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     ubraun@...ux.vnet.ibm.com
Cc:     netdev@...r.kernel.org, linux-s390@...r.kernel.org,
        schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
        stable@...r.kernel.org
Subject: Re: [PATCH net-next 13/13] s390/qeth: remove OSN-devices

From: Ursula Braun <ubraun@...ux.vnet.ibm.com>
Date: Wed, 11 Jan 2017 12:56:00 +0100

> CHPID type "OSN" is a device type which had been used by IBM product
> "Communication Controller for Linux". This product has reached end of
> service in March 2016. Thus OSN support can be removed from the qeth
> driver.
> 
> Signed-off-by: Ursula Braun <ubraun@...ux.vnet.ibm.com>
> Reviewed-by: Julian Wiedmann <jwi@...ux.vnet.ibm.com>
> Reviewed-by: Thomas Richter <tmricht@...ux.vnet.ibm.com>

IBM can certainly decide what physical products it wants to support
or not, but this doesn't directly apply to what the Linux kernel
driver supports.

We do not unilaterally remove support for a chip from a driver just
because the vendor decides to stop supporting that chip.  In fact this
is one of the main benefits and value-adds of Linux.

I'm not applying a patch series that removes support for a chipset
for this reason, sorry.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ