DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	"Rosen, Rami" <rami.rosen@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>, dpdk stable <stable@dpdk.org>,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/i40e: Fix a typo in i40e_flow.c.
Date: Tue, 28 Feb 2017 10:32:58 +0800	[thread overview]
Message-ID: <20170228023258.GF18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <9e1d25c2-d8be-e581-30e2-44703fc1ec2c@intel.com>

On Mon, Feb 27, 2017 at 04:31:28PM +0000, Ferruh Yigit wrote:
> On 2/27/2017 3:50 PM, Mcnamara, John wrote:
> > 
> > 
> >> -----Original Message-----
> >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rami Rosen
> >> Sent: Monday, February 27, 2017 4:54 AM
> >> To: dev@dpdk.org
> >> Cc: Rosen, Rami <rami.rosen@intel.com>
> >> Subject: [dpdk-dev] [PATCH] net/i40e: Fix a typo in i40e_flow.c.
> >>
> >> This patch fixes a trivial typo in i40e_flow.c.
> >>
> >> Signed-off-by: Rami Rosen <rami.rosen@intel.com>
> > 
> > Acked-by: John McNamara <john.mcnamara@intel.com>
> 
>     net/i40e: fix a typo in flow
> 
>     Fixes: 47c6782344b7 ("net/i40e: fix tunnel filter")
>     Fixes: d416530e6358 ("net/i40e: parse tunnel filter")
>     Cc: stable@dpdk.org

I think we don't have to put a (comment) typo fix patch into a stable
release, though it does no harm.

	--yliu

  reply	other threads:[~2017-02-28  2:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  4:53 [dpdk-dev] " Rami Rosen
2017-02-27 15:50 ` Mcnamara, John
2017-02-27 16:31   ` Ferruh Yigit
2017-02-28  2:32     ` Yuanhan Liu [this message]
2017-03-01 18:41       ` [dpdk-dev] [dpdk-stable] " 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=20170228023258.GF18844@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=rami.rosen@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas.monjalon@6wind.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).