From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/6] bnxt patch series
Date: Wed, 12 Jun 2019 16:41:34 +0100 [thread overview]
Message-ID: <5884bb74-6845-1bbc-0eb9-fb2f91c8703b@intel.com> (raw)
In-Reply-To: <20190608192208.77607-1-ajit.khaparde@broadcom.com>
On 6/8/2019 8:22 PM, Ajit Khaparde wrote:
> This is a patchset against dpdk-next-net tree on top of
> commit d800226ab9ede99ab9bc56a691555568e6e587f1.
> Please apply.
>
>
> Kalesh AP (1):
> net/bnxt: fix output of port xstats
>
> Naresh Kumar PBS (2):
> net/bnxt: fix interrupt vector array initialization
> net/bnxt: address build errors reported by intel compiler
>
> Somnath Kotur (3):
> net/bnxt: add code to redirect tunnel packets
> net/bnxt: fix to check for NULL completion ring doorbell in
> int_handler
> net/bnxt: driver to use configured MTU value during load
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-06-12 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 19:22 Ajit Khaparde
2019-06-08 19:22 ` [dpdk-dev] [PATCH 1/6] net/bnxt: add code to redirect tunnel packets Ajit Khaparde
2019-06-08 19:22 ` [dpdk-dev] [PATCH 2/6] net/bnxt: fix to check for NULL completion ring doorbell in int_handler Ajit Khaparde
2019-06-12 14:44 ` Ferruh Yigit
2019-06-12 14:49 ` Ferruh Yigit
2019-06-08 19:22 ` [dpdk-dev] [PATCH 3/6] net/bnxt: driver to use configured MTU value during load Ajit Khaparde
2019-06-08 19:22 ` [dpdk-dev] [PATCH 4/6] net/bnxt: fix output of port xstats Ajit Khaparde
2019-06-08 19:22 ` [dpdk-dev] [PATCH 5/6] net/bnxt: fix interrupt vector array initialization Ajit Khaparde
2019-06-08 19:22 ` [dpdk-dev] [PATCH 6/6] net/bnxt: address build errors reported by intel compiler Ajit Khaparde
2019-06-12 15:41 ` 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=5884bb74-6845-1bbc-0eb9-fb2f91c8703b@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).