From: Nandini Persad <nandinipersad361@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2] doc: reword flow offload and api docs
Date: Thu, 24 Apr 2025 16:21:58 +0000 [thread overview]
Message-ID: <DS7P223MB05259706BBBD7AAF31621176AD852@DS7P223MB0525.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250424090858.7ef78315@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Thanks Stephen. I think I know how to fix it. Might have to submit a new patch
________________________________
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Thursday, April 24, 2025 9:08:58 AM
To: Nandini Persad <nandinipersad361@gmail.com>
Cc: dev@dpdk.org <dev@dpdk.org>
Subject: Re: [PATCH v2] doc: reword flow offload and api docs
On Thu, 10 Apr 2025 11:39:31 -0700
Nandini Persad <nandinipersad361@gmail.com> wrote:
> I removed low level details of the code from the Flow Offload
> section of the Programmer's Guide so that it is more about
> the general usage of the APIs. I moved the specific details
> and definitions of the constants/function to the API docs
> if the details were not already there.
>
> Signed-off-by: Nandini Persad <nandinipersad361@gmail.com>
> ---
> doc/guides/prog_guide/ethdev/flow_offload.rst | 3584 +----------------
Looks good but does not apply cleanly to current main branch.
Tried manually fixing it but it was too hard and gave up.
[-- Attachment #2: Type: text/html, Size: 1747 bytes --]
prev parent reply other threads:[~2025-04-24 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 21:40 [PATCH] " Nandini Persad
2025-04-02 14:28 ` Stephen Hemminger
2025-04-10 18:39 ` [PATCH v2] " Nandini Persad
2025-04-24 16:08 ` Stephen Hemminger
2025-04-24 16:21 ` Nandini Persad [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=DS7P223MB05259706BBBD7AAF31621176AD852@DS7P223MB0525.NAMP223.PROD.OUTLOOK.COM \
--to=nandinipersad361@gmail.com \
--cc=dev@dpdk.org \
--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).