patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Walsh, Conor" <conor.walsh@intel.com>
To: Joyce Kong <joyce.kong@arm.com>, Ori Kam <orika@nvidia.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	Conor Fogarty <conor.fogarty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] examples/flow_filtering: fix wrong comment
Date: Thu, 4 Nov 2021 09:49:39 +0000	[thread overview]
Message-ID: <PH0PR11MB5207F08B014484E0A139F2D4FF8D9@PH0PR11MB5207.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211104073220.7938-1-joyce.kong@arm.com>

> From: Joyce Kong <joyce.kong@arm.com>
> Sent: Thursday 4 November 2021 07:32
> To: Ori Kam <orika@nvidia.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Conor Fogarty <conor.fogarty@intel.com>;
> Walsh, Conor <conor.walsh@intel.com>
> Cc: dev@dpdk.org; nd@arm.com; stable@dpdk.org
> Subject: [PATCH v2] examples/flow_filtering: fix wrong comment
> 
> Change the 'IPV4' level to 'ETH' level in the comment
> as it was previously misdescribed.
> 
> Fixes: 9a212dc06c7a ("doc: use code snippets in sample app guides")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Joyce Kong <joyce.kong@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> ---

Reviewed-by: Conor Walsh <conor.walsh@intel.com>

  reply	other threads:[~2021-11-04  9:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  2:41 [dpdk-stable] [PATCH v1] " Joyce Kong
2021-11-03  9:38 ` Walsh, Conor
2021-11-04  7:34   ` Joyce Kong
2021-11-04  9:49     ` Walsh, Conor
2021-11-04  7:32 ` [dpdk-stable] [PATCH v2] " Joyce Kong
2021-11-04  9:49   ` Walsh, Conor [this message]
2021-11-12  6:37 ` [PATCH v3] " Joyce Kong
2021-11-16 15:13   ` David Marchand

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=PH0PR11MB5207F08B014484E0A139F2D4FF8D9@PH0PR11MB5207.namprd11.prod.outlook.com \
    --to=conor.walsh@intel.com \
    --cc=conor.fogarty@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=joyce.kong@arm.com \
    --cc=nd@arm.com \
    --cc=orika@nvidia.com \
    --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).