From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/4] patches for bnxt
Date: Wed, 11 Oct 2017 03:08:10 +0100 [thread overview]
Message-ID: <48c1c8a2-c8ce-b9ee-737c-5c23364f3261@intel.com> (raw)
In-Reply-To: <20171010142303.17433-1-ajit.khaparde@broadcom.com>
On 10/10/2017 3:22 PM, Ajit Khaparde wrote:
> Patches against dpdk-next-net.
> Please apply.
>
> Ajit Khaparde (4):
> net/bnxt: fix cleanup if a filter allocation fails
> net/bnxt: prevent programming a duplicate flow
> net/bnxt: include fdir support
> net/bnxt: fix the association of a MACVLAN per VNIC
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-10-11 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 14:22 Ajit Khaparde
2017-10-10 14:23 ` [dpdk-dev] [PATCH 1/4] net/bnxt: fix cleanup if a filter allocation fails Ajit Khaparde
2017-10-10 14:23 ` [dpdk-dev] [PATCH 2/4] net/bnxt: prevent programming a duplicate flow Ajit Khaparde
2017-10-10 14:23 ` [dpdk-dev] [PATCH 3/4] net/bnxt: include fdir support Ajit Khaparde
2017-10-10 14:23 ` [dpdk-dev] [PATCH 4/4] net/bnxt: fix the association of a MACVLAN per VNIC Ajit Khaparde
2017-10-11 2:08 ` 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=48c1c8a2-c8ce-b9ee-737c-5c23364f3261@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).