From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, Leon Romanovsky <leon@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
Ira Weiny <ira.weiny@intel.com>,
"Fabio M . De Francesco" <fmdefrancesco@gmail.com>
Subject: Re: [PATCH net-next 0/5] Remove uses of kmap_atomic()
Date: Tue, 22 Nov 2022 13:06:09 -0800 [thread overview]
Message-ID: <b19e7bcb-e781-779c-0d2b-42b2e9b184fe@intel.com> (raw)
In-Reply-To: <20221122105059.7ef304ff@kernel.org>
On 11/22/2022 10:50 AM, Jakub Kicinski wrote:
> On Tue, 22 Nov 2022 13:29:03 +0200 Leon Romanovsky wrote:
>>> drivers/net/ethernet/sun/cassini.c | 40 ++++++-------------
>>> drivers/net/ethernet/sun/sunvnet_common.c | 4 +-
>>
>> Dave, Jakub, Paolo
>> I wonder if these drivers can be simply deleted.
>
> My thought as well. It's just a matter of digging thru the history,
> platform code and the web to find potential users and contacting them.
I did a little bit of digging on these two files. Here's what I found.
For the cassini driver, I don't see any recent patches that fix an end
user visible issue. There are clean ups, updates to use newer kernel
APIs, and some build/memory leak fixes. I checked as far back as 2011.
There are web references to some issues in kernel v2.6. I didn't see
anything more recent.
The code in sunvnet_common.c seems to be common code that's used by
[1] "Sun4v LDOM Virtual Switch Driver" (ldmvsw.c, kconfig flag
CONFIG_LDMVSW)
[2] "Sun LDOM virtual network driver" (sunvnet.c, kconfig flag
CONFIG_SUNVNET).
These two seem to have had some feature updates around 2017, but
otherwise the situation is the same as cassini.
Ani
next prev parent reply other threads:[~2022-11-22 21:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 22:25 [PATCH net-next 0/5] Remove uses of kmap_atomic() Anirudh Venkataramanan
2022-11-17 22:25 ` [PATCH net-next 1/5] ch_ktls: Use kmap_local_page() instead " Anirudh Venkataramanan
2022-11-18 8:14 ` Fabio M. De Francesco
2022-11-18 18:27 ` Anirudh Venkataramanan
2022-11-18 20:18 ` Fabio M. De Francesco
2022-11-18 20:38 ` Anirudh Venkataramanan
2022-11-19 1:22 ` Ira Weiny
2022-11-17 22:25 ` [PATCH net-next 2/5] sfc: " Anirudh Venkataramanan
2022-11-18 8:23 ` Fabio M. De Francesco
2022-11-18 17:47 ` Anirudh Venkataramanan
2022-11-18 19:26 ` Fabio M. De Francesco
2022-11-18 20:34 ` Anirudh Venkataramanan
2022-11-19 1:25 ` Ira Weiny
2022-11-17 22:25 ` [PATCH net-next 3/5] cassini: Remove unnecessary use " Anirudh Venkataramanan
2022-11-18 8:35 ` Fabio M. De Francesco
2022-11-18 17:55 ` Anirudh Venkataramanan
2022-11-18 20:30 ` Fabio M. De Francesco
2022-11-17 22:25 ` [PATCH net-next 4/5] cassini: Use kmap_local_page() instead " Anirudh Venkataramanan
2022-11-18 8:53 ` Fabio M. De Francesco
2022-11-17 22:25 ` [PATCH net-next 5/5] sunvnet: " Anirudh Venkataramanan
2022-11-18 9:11 ` Fabio M. De Francesco
2022-11-18 20:45 ` Fabio M. De Francesco
2022-11-19 0:47 ` Anirudh Venkataramanan
2022-11-22 11:29 ` [PATCH net-next 0/5] Remove uses " Leon Romanovsky
2022-11-22 18:50 ` Jakub Kicinski
2022-11-22 21:06 ` Anirudh Venkataramanan [this message]
2022-11-23 7:34 ` Leon Romanovsky
2022-11-23 18:38 ` Anirudh Venkataramanan
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=b19e7bcb-e781-779c-0d2b-42b2e9b184fe@intel.com \
--to=anirudh.venkataramanan@intel.com \
--cc=davem@davemloft.net \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).