linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
To: <karl.volz@oracle.com>, <netdev@vger.kernel.org>
Cc: <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 0/7] Remove three Sun net drivers
Date: Fri, 6 Jan 2023 15:10:55 -0800	[thread overview]
Message-ID: <048ca2e1-4490-21da-b95f-8be018d64e5a@intel.com> (raw)
In-Reply-To: <c43562d7-8e6b-40d9-26dc-ab85afcef70e@oracle.com>

On 1/6/2023 2:44 PM, Karl Volz wrote:
> 
> 
> On 1/6/23 15:00, Anirudh Venkataramanan wrote:
>> This series removes the Sun Cassini, LDOM vswitch and sunvnet drivers.
>>
>> 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.
>>
>> The idea behind putting out this series is to either establish that these
>> drivers are used and should be maintained, or remove them.
> Anirudh,
> 
> The Sun LDOM vswitch and sunvnet drivers are still in use, please do not 
> remove them or the event tracing.
> We use them internally and you don't see any discussions because they 
> generally work fine (AFAIK).

Hello Karl,

Thanks for chiming in.

Are there recent platforms where these drivers are used? If yes, do you 
know which ones? Or are these drivers useful in old/legacy platforms 
that are still around but perhaps no longer in production?

> I think you are also going to break things by removing Sun Cassini 
> support, but I am not using it personally.

You suspect there are users for this driver as well?

> What user visible bugs are you referring to here?

I was saying I don't see any evidence of recent bug fixes, which would 
make sense if these drivers "just work".

Ani

  reply	other threads:[~2023-01-06 23:11 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 [this message]
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=048ca2e1-4490-21da-b95f-8be018d64e5a@intel.com \
    --to=anirudh.venkataramanan@intel.com \
    --cc=karl.volz@oracle.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=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).