From: Jacob Keller <jacob.e.keller@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 4/4] iavf: delete the iavf client interface
Date: Tue, 17 Oct 2023 10:46:40 -0700 [thread overview]
Message-ID: <709736fb-a2a5-4d8b-a1a4-52418a172fb8@intel.com> (raw)
In-Reply-To: <20231016164849.45691-5-mschmidt@redhat.com>
On 10/16/2023 9:48 AM, Michal Schmidt wrote:
> The iavf client interface was added in 2017 by commit ed0e894de7c1
> ("i40evf: add client interface"), but there have never been any in-tree
> callers.
>
> It's not useful for future development either. The Intel out-of-tree
> iavf and irdma drivers instead use an auxiliary bus, which is a better
> solution.
>
> Remove the iavf client interface code. Also gone are the client_task
> work and the client_lock mutex.
>
> Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
> ---
Yea this interface is not supported by any current out-of-tree driver I
could find either. From what I can tell the last version of out-of-tree
iAVF which shipped this interface was 2021, iavf 4.2.1, which appears to
have released in 2021.
I was unable to determine when the last time any software which used
this interface was supported... It appears to have never been used
in-tree at all.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-10-17 17:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 16:48 [Intel-wired-lan] [PATCH iwl-next 0/4] iavf: cleanups, dead code removal Michal Schmidt
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 1/4] iavf: rely on netdev's own registered state Michal Schmidt
2023-10-17 8:01 ` Drewek, Wojciech
2023-10-17 17:30 ` Jacob Keller
2023-10-24 9:09 ` Romanowski, Rafal
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 2/4] iavf: use unregister_netdev Michal Schmidt
2023-10-17 8:06 ` Drewek, Wojciech
2023-10-24 9:11 ` Romanowski, Rafal
2023-10-17 17:33 ` Jacob Keller
2023-10-17 18:43 ` Jacob Keller
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 3/4] iavf: add a common function for undoing the interrupt scheme Michal Schmidt
2023-10-17 8:58 ` Drewek, Wojciech
2023-10-17 17:35 ` Jacob Keller
2023-10-24 9:12 ` Romanowski, Rafal
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 4/4] iavf: delete the iavf client interface Michal Schmidt
2023-10-17 17:46 ` Jacob Keller [this message]
2023-10-24 9:12 ` Romanowski, Rafal
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=709736fb-a2a5-4d8b-a1a4-52418a172fb8@intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@osuosl.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