DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Beilei Xing <beilei.xing@intel.com>, jingjing.wu@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: add checking invalid VF queue id for FDIR
Date: Tue, 18 Jul 2017 11:23:05 +0100	[thread overview]
Message-ID: <eeb73761-b5fd-712e-750f-560a1dd9f365@intel.com> (raw)
In-Reply-To: <1500015096-58857-1-git-send-email-beilei.xing@intel.com>

On 7/14/2017 7:51 AM, Beilei Xing wrote:
> There's only invalid queue id checking for PF when creating FDIR
> rules, this patch adds checking invalid queue id for VF.
> 
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>

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

      reply	other threads:[~2017-07-18 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14  6:41 [dpdk-dev] [PATCH] net/i40e: add invalid queue id checking for VF Beilei Xing
2017-07-14  6:51 ` [dpdk-dev] [PATCH v2] net/i40e: add checking invalid VF queue id for FDIR Beilei Xing
2017-07-18 10:23   ` Ferruh Yigit [this message]

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=eeb73761-b5fd-712e-750f-560a1dd9f365@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.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).