From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, corbet@lwn.net, jdmason@kudzu.us,
vburru@marvell.com, jiawenwu@trustnetic.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] eth: remove neterion/vxge
Date: Fri, 1 Jul 2022 12:34:13 +0200 [thread overview]
Message-ID: <Yr7NpQz6/esZAiZv@nanopsycho> (raw)
In-Reply-To: <20220701044234.706229-1-kuba@kernel.org>
Fri, Jul 01, 2022 at 06:42:34AM CEST, kuba@kernel.org wrote:
>The last meaningful change to this driver was made by Jon in 2011.
>As much as we'd like to believe that this is because the code is
>perfect the chances are nobody is using this hardware.
Hmm, I can understand what for driver for HW that is no longer
developed, the driver changes might be very minimal. The fact that the
code does not change for years does not mean that there are users of
this NIC which this patch would break :/
Isn't there some obsoletion scheme globally applied to kernel device
support? I would expect something like that.
next prev parent reply other threads:[~2022-07-01 10:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 4:42 [PATCH net-next] eth: remove neterion/vxge Jakub Kicinski
2022-07-01 10:34 ` Jiri Pirko [this message]
2022-07-01 13:17 ` David Lamparter
2022-07-01 14:06 ` Jiri Pirko
2022-07-01 14:11 ` David Lamparter
2022-07-01 16:15 ` Jakub Kicinski
2022-07-04 8:24 ` Martin Habets
2022-07-01 17:12 ` Francois Romieu
2022-07-01 21:40 ` Jakub Kicinski
2022-07-05 6:17 ` Paolo Abeni
2022-07-05 18:06 ` Jakub Kicinski
2022-07-05 18:27 ` Stephen Hemminger
2022-07-06 0:44 ` Francois Romieu
2022-07-05 23:00 ` patchwork-bot+netdevbpf
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=Yr7NpQz6/esZAiZv@nanopsycho \
--to=jiri@resnulli.us \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdmason@kudzu.us \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vburru@marvell.com \
/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