patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 1/2] net/enic: fix hardcoding of some flow director masks
Date: Fri, 3 Feb 2017 22:54:04 +0000	[thread overview]
Message-ID: <a998a9e4-2274-4eea-f800-6ecc3be49e0c@intel.com> (raw)
In-Reply-To: <20170203095446.4614-1-johndale@cisco.com>

On 2/3/2017 9:54 AM, John Daley wrote:
> Hard coded mask values were being used for several of the IPv4 and IPv6
> fields. Use the values in the rte_eth_fdir_masks structure provided by the
> caller.
> 
> Fixes: dfbd6a9cb504 ("net/enic: extend flow director support for 1300 series") 
> Cc: stable@dpdk.org

> Signed-off-by: John Daley <johndale@cisco.com>

Series applied to dpdk-next-net/master, thanks.

  parent reply	other threads:[~2017-02-03 22:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03  9:54 John Daley
2017-02-03  9:54 ` [dpdk-stable] [PATCH 2/2] net/enic: fix flow director IPv6 traffic class specification John Daley
2017-02-03 22:54 ` Ferruh Yigit [this message]
     [not found] ` <20170209003130.17245-1-johndale@cisco.com>
2017-02-09  0:31   ` [dpdk-stable] [PATCH v2] net/enic: fix hardcoding of some flow director masks John Daley
     [not found] ` <20170209004009.26242-1-johndale@cisco.com>
2017-02-09  0:40   ` John Daley
2017-02-09 10:16     ` Ferruh Yigit
2017-02-09 17:43       ` John Daley (johndale)
2017-02-09 17:58         ` Ferruh Yigit
2017-02-09 12:21     ` Ferruh Yigit
  -- strict thread matches above, loose matches on Subject: below --
2017-02-03  9:52 [dpdk-stable] [PATCH 1/2] " John Daley

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=a998a9e4-2274-4eea-f800-6ecc3be49e0c@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=johndale@cisco.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).