From: Stephen Hemminger <stephen@networkplumber.org>
To: Ed Czeck <ed.czeck@atomicrules.com>
Cc: dev@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>,
John Miller <john.miller@atomicrules.com>
Subject: Re: [PATCH v3 1/4] net/ark: add PCIe IDS for newly supported devices
Date: Mon, 15 Sep 2025 08:36:18 -0700 [thread overview]
Message-ID: <20250915083618.6573c808@hermes.local> (raw)
In-Reply-To: <20250915150204.1719628-1-ed.czeck@atomicrules.com>
On Mon, 15 Sep 2025 11:02:01 -0400
Ed Czeck <ed.czeck@atomicrules.com> wrote:
> Update documentation and release notes
> update link speed capabilities for 200G and 400G
>
> Signed-off-by: Ed Czeck <ed.czeck@atomicrules.com>
> ---
Patches queued to next-net
prev parent reply other threads:[~2025-09-15 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 21:28 [PATCH " Ed Czeck
2025-09-03 21:28 ` [PATCH 2/4] net/ark: remove double mbuf frees Ed Czeck
2025-09-03 21:28 ` [PATCH 3/4] net/ark: improve ring handling for segmented packets Ed Czeck
2025-09-03 21:28 ` [PATCH 4/4] net/ark: improve Rx queue recovery after mbuf exhaustion Ed Czeck
2025-09-06 4:51 ` Stephen Hemminger
2025-09-10 0:33 ` Stephen Hemminger
2025-09-10 0:33 ` Stephen Hemminger
2025-09-10 19:04 ` [PATCH v2 1/4] net/ark: add PCIe IDS for newly supported devices Ed Czeck
2025-09-10 19:04 ` [PATCH v2 2/4] net/ark: remove double mbuf frees Ed Czeck
2025-09-10 19:04 ` [PATCH v2 3/4] net/ark: improve ring handling for segmented packets Ed Czeck
2025-09-10 19:04 ` [PATCH v2 4/4] net/ark: improve Rx queue recovery after mbuf exhaustion Ed Czeck
2025-09-15 15:02 ` [PATCH v3 1/4] net/ark: add PCIe IDS for newly supported devices Ed Czeck
2025-09-15 15:02 ` [PATCH v3 2/4] net/ark: remove double mbuf frees Ed Czeck
2025-09-15 15:02 ` [PATCH v3 3/4] net/ark: improve ring handling for segmented packets Ed Czeck
2025-09-15 15:02 ` [PATCH v3 4/4] net/ark: improve Rx queue recovery after mbuf exhaustion Ed Czeck
2025-09-15 15:36 ` Stephen Hemminger [this message]
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=20250915083618.6573c808@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=john.miller@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).