[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <69E3975E-A4D0-4472-80F0-9FAB2E0024FA@microgate.com>
Date: Thu, 5 Nov 2020 01:39:36 -0800
From: Paul Fulghum <paulkf@...rogate.com>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: Lee Jones <lee.jones@...aro.org>,
"linux-kernel@...r.kernel.org Mailing List"
<linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 27/36] tty: synclinkmp: Mark never checked 'readval' as
__always_unused
> On Nov 5, 2020, at 1:10 AM, Jiri Slaby <jirislaby@...nel.org> wrote:
>
> OK, let the loop alone. I would bet a half a pig that noone is able to test this driver. But one has to write this for someone to raise and admit they are still using it. In fact, there are _4_ google replies to "Microgate Corporation" "SyncLink Multiport Adapter" "lspci".
The hardware used with synclink.c and synclinkmp.c has not been manufactured for 15 years and was low volume. The chances of either driver still being in use is very low. Not even Microgate (me) has the ability to test either anymore (no hardware). I don’t know the policy about driver removal, but I think both could be removed without upsetting anyone.
synclink_gt.c is still in production and the driver still actively used.
If there are no objections to removing the the old drivers (synclink.c/synclink_mp.c) I could make a patch to do so tomorrow (it is 1:30am here now). Nothing eliminates niggling warnings like removing dead code.
Powered by blists - more mailing lists