DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahed Shaikh <shshaikh@marvell.com>, dev@dpdk.org
Cc: rmody@marvell.com, GR-Everest-DPDK-Dev@marvell.com
Subject: Re: [dpdk-dev] [PATCH 1/1] net/qede: update feature support matrix with flow API
Date: Fri, 12 Apr 2019 19:03:04 +0100	[thread overview]
Message-ID: <e16c3e00-9dff-5303-284b-17f961bc8fbf@intel.com> (raw)
Message-ID: <20190412180304.4zHvtNwZD0odZLeALfAncA-8NMVclUPyt90qA5t1SgY@z> (raw)
In-Reply-To: <20190412101237.14093-1-shshaikh@marvell.com>

On 4/12/2019 11:12 AM, Shahed Shaikh wrote:
> Commit 267d32de46a8 ("net/qede: support generic flow API")
> added a support for RTE_FLOW APIs but did not update the feature
> support matrix.
> 
> Fixes: 267d32de46a8 ("net/qede: support generic flow API")
> 
> Signed-off-by: Shahed Shaikh <shshaikh@marvell.com>

Applied to dpdk-next-net/master, thanks.

  parent reply	other threads:[~2019-04-12 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 10:12 Shahed Shaikh
2019-04-12 10:12 ` Shahed Shaikh
2019-04-12 18:03 ` Ferruh Yigit [this message]
2019-04-12 18:03   ` 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=e16c3e00-9dff-5303-284b-17f961bc8fbf@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=dev@dpdk.org \
    --cc=rmody@marvell.com \
    --cc=shshaikh@marvell.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).