From: Ivan Malov <ivan.malov@arknetworks.am>
To: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Cc: Pieter Jansen Van Vuuren <pieter.jansen-van-vuuren@amd.com>,
Andy Moreton <andy.moreton@amd.com>
Subject: AMD Solarflare PMD roadmap for 25.11
Date: Fri, 29 Aug 2025 02:45:38 +0400 (+04) [thread overview]
Message-ID: <cbf6f000-0119-39a6-c262-9c1375c78060@arknetworks.am> (raw)
This communication hereby serves as notification that the following patch sets,
as described herein, are the candidates for orderly inclusion in 25.11 release.
1. common/sfc_efx/base: link stability improvements for X4 NICs
common/sfc_efx/base: fix autoneg detection with netport MCDI
common/sfc_efx/base: default to auto fcntl with netport MCDI
common/sfc_efx/base: fix auto FEC selection for netport MCDI
common/sfc_efx/base: use auto FEC on start with netport MCDI
2. common/sfc_efx/base: sync DPDK with the in-house libefx repo
Please be informed that series (1) is in its final preparation stages and will
be shipped in early September. Series (2) might become ready by late September.
Thank you.
reply other threads:[~2025-08-28 22:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cbf6f000-0119-39a6-c262-9c1375c78060@arknetworks.am \
--to=ivan.malov@arknetworks.am \
--cc=andy.moreton@amd.com \
--cc=dev@dpdk.org \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=stephen@networkplumber.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).