netdev - Re: [PATCH net-next 1/7] ethernet: Remove the Sun Cassini driver

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: <b9284d54-3153-e074-8a07-0812b26fd290@intel.com>
Date:   Sat, 7 Jan 2023 11:16:20 -0800
From:   Anirudh Venkataramanan <anirudh.venkataramanan@...el.com>
To:     Anatoly Pugachev <matorola@...il.com>
CC:     <netdev@...r.kernel.org>, <linux-pci@...r.kernel.org>,
        <linuxppc-dev@...ts.ozlabs.org>, <linux-mips@...r.kernel.org>,
        <linux-trace-kernel@...r.kernel.org>, <sparclinux@...r.kernel.org>,
        "Leon Romanovsky" <leon@...nel.org>
Subject: Re: [PATCH net-next 1/7] ethernet: Remove the Sun Cassini driver

On 1/7/2023 4:25 AM, Anatoly Pugachev wrote:
> On Sat, Jan 7, 2023 at 1:00 AM Anirudh Venkataramanan
> <anirudh.venkataramanan@...el.com> wrote:
>>
>> In a recent patch series that touched this driver [1], it was suggested
>> that this driver should be removed completely. git logs suggest that
>> there hasn't been any significant feature addition, improvement or fixes to
>> user-visible bugs in a while. A web search didn't indicate any recent
>> discussions or any evidence that there are users out there who care about
>> this driver. Thus, remove this driver.
>>
>> Notes:
>>
>> checkpatch complains "WARNING: added, moved or deleted file(s), does
>> MAINTAINERS need updating?". The files being removed don't have their
>> own entries in the MAINTAINERS file, so there's nothing to remove.
>>
>> checkpatch also complains about the long lore link below.
>>
>> [1] https://lore.kernel.org/netdev/99629223-ac1b-0f82-50b8-ea307b3b0197@intel.com/T/#t
>>
>> Suggested-by: Leon Romanovsky <leon@...nel.org>
>> Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@...el.com>
> 
> Do we drop/delete a working functionality by only taking in account
> git activity ?

No, but in some cases it's enough to at least start asking the "who uses 
this code? should we continue maintaining it?" type questions.

In the cover letter I did say this:

"The idea behind putting out this series is to either establish that 
these drivers are used and should be maintained, or remove them."

We have established that these drivers are indeed used, and thus 
shouldn't be removed.

> 
> What is a proper way to decline patch series (vs Acked-by) ?

There's no tag that I am aware of. I have seen people say "NACK" or 
"please don't do this" followed by an explanation of why the 
patch/series is a bad idea. For example, see the other responses to this 
series.

Ani