linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Cc: Leon Romanovsky <leon@kernel.org>,
	netdev@vger.kernel.org,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	linux-mips@vger.kernel.org, linux-pci@vger.kernel.org,
	sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] Remove three Sun net drivers
Date: Fri, 6 Jan 2023 18:15:40 -0800	[thread overview]
Message-ID: <20230106181540.61d4cad0@kernel.org> (raw)
In-Reply-To: <50dfdff7-81c7-ab40-a6c5-e5e73959b780@intel.com>

On Fri, 6 Jan 2023 18:04:54 -0800 Anirudh Venkataramanan wrote:
> >> In a recent patch series that touched these drivers [1], it was suggested
> >> that these drivers 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
> >> these drivers.  
> > 
> > Well, these drivers just work and I don't see why there should be regular
> > discussions about them or changes.  
> 
> That's fair, but lack of discussion can also be signs of disuse, and 
> that's really the hunch I was following up on.

Lack of feedback, too. Some of these drivers are missing entries 
in MAINTAINERS and patches don't get review tags from anyone.

  reply	other threads:[~2023-01-07  2: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
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 [this message]
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=20230106181540.61d4cad0@kernel.org \
    --to=kuba@kernel.org \
    --cc=anirudh.venkataramanan@intel.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --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=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).