From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/4] patch series for bnxt
Date: Thu, 5 Oct 2017 21:38:20 +0100 [thread overview]
Message-ID: <613d87b2-eb9a-7c9b-68f2-10ddeea99ad1@intel.com> (raw)
In-Reply-To: <20171005150646.3188-1-ajit.khaparde@broadcom.com>
On 10/5/2017 4:06 PM, Ajit Khaparde wrote:
> A continuation of the previous submission,
> this patchset adds support for ntuple filtering.
> It also fixes an issue found while testing VMDQ
> and updates bnxt.ini
> The last patch removes some unnecessary parentheses from the code.
>
> Ajit Khaparde (4):
> net/bnxt: add ntuple filtering support
> net/bnxt: fix number of mac addresses for VMDQ support
> net/bnxt: fixup bnxt.ini
> net/bnxt: fix some unnecessary parentheses
Series applied to dpdk-next-net/master, thanks.
Except last one.
Last one squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2017-10-05 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 14:28 [dpdk-dev] [PATCH 0/3] " Ajit Khaparde
2017-10-05 14:28 ` [dpdk-dev] [PATCH 1/3] net/bnxt: add ntuple filtering support Ajit Khaparde
2017-10-05 14:28 ` [dpdk-dev] [PATCH 2/3] net/bnxt: fix number of mac addresses for VMDQ support Ajit Khaparde
2017-10-05 14:28 ` [dpdk-dev] [PATCH 3/3] net/bnxt: fixup bnxt.ini Ajit Khaparde
2017-10-05 15:06 ` [dpdk-dev] [PATCH v2 0/4] patch series for bnxt Ajit Khaparde
2017-10-05 15:06 ` [dpdk-dev] [PATCH v2 1/4] net/bnxt: add ntuple filtering support Ajit Khaparde
2017-10-05 15:06 ` [dpdk-dev] [PATCH v2 2/4] net/bnxt: fix number of mac addresses for VMDQ support Ajit Khaparde
2017-10-05 15:06 ` [dpdk-dev] [PATCH v2 3/4] net/bnxt: fixup bnxt.ini Ajit Khaparde
2017-10-05 15:06 ` [dpdk-dev] [PATCH v2 4/4] net/bnxt: fix some unnecessary parentheses Ajit Khaparde
2017-10-05 20:38 ` 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=613d87b2-eb9a-7c9b-68f2-10ddeea99ad1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@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).