patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Ali Alnubani <alialnu@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Yigit, Ferruh" <Ferruh.Yigit@amd.com>
Subject: RE: [PATCH] doc: fix typos and wording in flow API guide
Date: Thu, 13 Jul 2023 16:50:23 +0000	[thread overview]
Message-ID: <PH8PR11MB68048EED31ADC0F805F600CAFC37A@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230703075827.503040-1-alialnu@nvidia.com>


> -----Original Message-----
> From: Ali Alnubani <alialnu@nvidia.com>
> Sent: Monday, July 3, 2023 8:58 AM
> To: dev@dpdk.org
> Cc: Doherty, Declan <declan.doherty@intel.com>; stable@dpdk.org
> Subject: [PATCH] doc: fix typos and wording in flow API guide
> 
> This fixes typos, punctuation and wording in the rte flow API guide.
> 
> Fixes: 2f82d143fb31 ("ethdev: add group jump action")
> Cc: declan.doherty@intel.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ali Alnubani <alialnu@nvidia.com>


> -Group 0 is the default group and this is the only group which flows
> +Group 0 is the default group and is the only group where flows are

Slightly better is s/where flows/that flows/

With, or without that change:

Acked-by: John McNamara <john.mcnamara@intel.com>




  parent reply	other threads:[~2023-07-13 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  7:58 Ali Alnubani
2023-07-04 14:05 ` Ferruh Yigit
2023-07-13 16:50 ` Mcnamara, John [this message]
2023-07-16  6:58 ` [PATCH v2] " Ali Alnubani
2023-07-17 10:50   ` Ferruh Yigit

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=PH8PR11MB68048EED31ADC0F805F600CAFC37A@PH8PR11MB6804.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=Ferruh.Yigit@amd.com \
    --cc=alialnu@nvidia.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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).