From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Reshma Pattan <reshma.pattan@intel.com>
Subject: Re: [PATCH v3 8/8] doc: update documentation on pdump library
Date: Tue, 21 Oct 2025 08:11:21 -0700 [thread overview]
Message-ID: <20251021081121.2168f35d@phoenix.lan> (raw)
In-Reply-To: <20251019165728.164929-9-stephen@networkplumber.org>
On Sun, 19 Oct 2025 09:56:15 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> The documentation was missing some of the API, and had some
> awkward wording. With the help of ChatGPT, update it and make
> it more concise.
>
> Add a release note
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Recheck-request: iol-compile-amd64-testing, github-robot, intel-Functional
next prev parent reply other threads:[~2025-10-21 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <250811213632.16023-1-stephen@networkplumber.org>
2025-10-19 16:56 ` [PATCH v3 0/8] packet capture bugfix and improvements Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 1/8] dumpcap: handle primary process exit Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 2/8] pdump: " Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 3/8] pdump: fix races in callbacks Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 4/8] dumpcap: handle pdump requests from primary Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 5/8] pdump: " Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 6/8] pdump: forward callback enable to secondary Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 7/8] pdump: remove use of VLA Stephen Hemminger
2025-10-19 16:56 ` [PATCH v3 8/8] doc: update documentation on pdump library Stephen Hemminger
2025-10-21 15:11 ` Stephen Hemminger [this message]
2025-10-22 17:29 ` [PATCH v3 0/8] packet capture bugfix and improvements Patrick Robb
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=20251021081121.2168f35d@phoenix.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.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).