DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Nandini Persad <nandinipersad361@gmail.com>
Cc: Ori Kam <orika@nvidia.com>, Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	dev@dpdk.org
Subject: Re: [PATCH] doc: reword flow offload and api docs
Date: Wed, 2 Apr 2025 07:28:38 -0700	[thread overview]
Message-ID: <20250402072838.6479484c@hermes.local> (raw)
In-Reply-To: <20250331214036.17295-1-nandinipersad361@gmail.com>

On Mon, 31 Mar 2025 14:40:36 -0700
Nandini Persad <nandinipersad361@gmail.com> wrote:

> I removed low level details of the code and simplified the
> Flow Offload section of Programmer's Guide to be more about the
> general usage of the APIs. The specifics were moved to API docs if
> the details did not already exist there.
> 
> Signed-off-by: Nandini Persad <nandinipersad361@gmail.com>
> ---

Looks good, fix the spelling errors and resubmit please.

WARNING:TYPO_SPELLING: 'wih' may be misspelled - perhaps 'with'?
#3558: FILE: doc/guides/prog_guide/ethdev/flow_offload.rst:579:
+- Flush: The function ``rte_flow_flush`` destroys all flow rules associated wih a port.

WARNING:TYPO_SPELLING: 'behvaior' may be misspelled - perhaps 'behaviour'?
#4142: FILE: lib/ethdev/rte_flow.h:4403:
+ * is missing at the specified index, then the behvaior is undefined and

total: 0 errors, 2 warnings, 4087 lines checked

      reply	other threads:[~2025-04-02 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 21:40 Nandini Persad
2025-04-02 14:28 ` 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=20250402072838.6479484c@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=nandinipersad361@gmail.com \
    --cc=orika@nvidia.com \
    --cc=thomas@monjalon.net \
    /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).