From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
To: Anatoly Pugachev <matorola@gmail.com>
Cc: <netdev@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-mips@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>,
<sparclinux@vger.kernel.org>, "Leon Romanovsky" <leon@kernel.org>
Subject: Re: [PATCH net-next 1/7] ethernet: Remove the Sun Cassini driver
Date: Sat, 7 Jan 2023 11:16:20 -0800 [thread overview]
Message-ID: <b9284d54-3153-e074-8a07-0812b26fd290@intel.com> (raw)
In-Reply-To: <CADxRZqw2K1QT2cEa6U_4DUxgYrwMiZzU4Qy6iXVm2WRTYVa=xw@mail.gmail.com>
On 1/7/2023 4:25 AM, Anatoly Pugachev wrote:
> On Sat, Jan 7, 2023 at 1:00 AM Anirudh Venkataramanan
> <anirudh.venkataramanan@intel.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@kernel.org>
>> Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.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
next prev parent reply other threads:[~2023-01-07 19:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 22:00 [PATCH net-next 0/7] Remove three Sun net drivers Anirudh Venkataramanan
2023-01-06 22:00 ` [PATCH net-next 1/7] ethernet: Remove the Sun Cassini driver Anirudh Venkataramanan
2023-01-07 12:25 ` Anatoly Pugachev
2023-01-07 19:16 ` Anirudh Venkataramanan [this message]
2023-01-06 22:00 ` [PATCH net-next 2/7] PCI: Remove PCI IDs used by " Anirudh Venkataramanan
2023-01-10 15:26 ` Bjorn Helgaas
2023-01-10 16:51 ` Anirudh Venkataramanan
2023-01-06 22:00 ` [PATCH net-next 3/7] powerpc: configs: Remove reference to CONFIG_CASSINI Anirudh Venkataramanan
2023-01-06 22:00 ` [PATCH net-next 4/7] mips: " Anirudh Venkataramanan
2023-01-06 22:00 ` [PATCH net-next 5/7] ethernet: Remove the Sun LDOM vswitch and sunvnet drivers Anirudh Venkataramanan
2023-01-06 22:00 ` [PATCH net-next 6/7] sunvnet: Remove event tracing file Anirudh Venkataramanan
2023-01-06 22:00 ` [PATCH net-next 7/7] sparc: configs: Remove references to CONFIG_SUNVNET and CONFIG_LDMVSW Anirudh Venkataramanan
2023-01-07 12:14 ` Anatoly Pugachev
2023-01-06 22:44 ` [PATCH net-next 0/7] Remove three Sun net drivers Karl Volz
2023-01-06 23:10 ` Anirudh Venkataramanan
2023-01-06 23:25 ` Karl Volz
2023-01-07 1:36 ` John Paul Adrian Glaubitz
2023-01-07 2:04 ` Anirudh Venkataramanan
2023-01-07 2:15 ` Jakub Kicinski
2023-01-07 2:24 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9284d54-3153-e074-8a07-0812b26fd290@intel.com \
--to=anirudh.venkataramanan@intel.com \
--cc=leon@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matorola@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).