From: Bruce Richardson <bruce.richardson@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [v2 00/15] bnxt patch series
Date: Fri, 30 Sep 2016 11:32:40 +0100 [thread overview]
Message-ID: <20160930103239.GA58652@bricha3-MOBL3> (raw)
In-Reply-To: <20160926161333.GA28141@C02PT1RBG8WP.aus.broadcom.com>
On Mon, Sep 26, 2016 at 11:13:33AM -0500, Ajit Khaparde wrote:
> Please consider applying this patch series.
>
> v1->v2: Update the bnxt PMD to use a newer HWRM API
> has been split into smaller patches for easier review.
>
> Ajit Khaparde (15):
> bnxt: Add support for Broadcom StrataGX Communication Processors
> bnxt: Enable support for NPAR 1.0 feature
> bnxt: Add support for new DIDs
> bnxt: Update Broadcom PMD driver documentation
> bnxt: Add support to load bnxt PMD on a SR-IOV VF
> bnxt: Add support for port hotplug
> bnxt: Update the bnxt PMD to use the 1.5.1 HWRM API
> bnxt: Update buffer descriptor definitions per 1.5.1 API
> bnxt: Update various completion descriptors as per the 1.5.1 HWRM API
> bnxt: Update various structures to version 1.5.1 of HWRM API
> bnxt: Update some structures to use the 1.5.1 HWRM API
> bnxt: Update the VNIC related structures to the 1.5.1 HWRM version
> bnxt: Update the HWRM ring related structures to version 1.5.1
> bnxt: Update the HWRM filter related structures to version 1.5.1
> bnxt: Update struct definitions to use the 1.5.1 HWRM API
>
Applied to dpdk-next-net/rel_16_11
Thanks,
/Bruce
prev parent reply other threads:[~2016-09-30 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 16:13 Ajit Khaparde
2016-09-26 16:46 ` Ferruh Yigit
2016-09-30 10:32 ` Bruce Richardson [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=20160930103239.GA58652@bricha3-MOBL3 \
--to=bruce.richardson@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).