From: "He, Shaopeng" <shaopeng.he@intel.com>
To: "Qiu, Michael" <michael.qiu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] Intel new NIC Boulder Rapid support
Date: Wed, 28 Oct 2015 08:29:11 +0000 [thread overview]
Message-ID: <FB82FCC69332B84596FE0CEC3C131094AF94DC@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1445835236-30374-1-git-send-email-michael.qiu@intel.com>
> -----Original Message-----
> From: Qiu, Michael
> Sent: Monday, October 26, 2015 12:54 PM
> To: dev@dpdk.org
> Cc: He, Shaopeng; Chen, Jing D; Qiu, Michael
> Subject: [PATCH v2 0/2] Intel new NIC Boulder Rapid support
>
> Boulder Rapid is a new 100G NIC of Intel fm10k family, this patch set enable it
> in DPDK.
>
> change log:
> V2 --> v1
> update the release notes
>
> Michael Qiu (2):
> fm10k: add Intel Boulder Rapid NIC support
> doc: release note update for Boulder Rapid Support
>
> doc/guides/rel_notes/release_2_2.rst | 3 +++
> drivers/net/fm10k/base/fm10k_osdep.h | 4 ++++
> lib/librte_eal/common/include/rte_pci_dev_ids.h | 2 ++
> 3 files changed, 9 insertions(+)
>
> --
> 1.9.3
Acked-by : Shaopeng He <shaopeng.he@intel.com>
next prev parent reply other threads:[~2015-10-28 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 2:31 [dpdk-dev] [PATCH] fm10k: add Intel Boulder Rapid NIC support Michael Qiu
2015-10-15 5:25 ` Chen, Jing D
2015-10-19 8:44 ` He, Shaopeng
2015-10-26 4:53 ` [dpdk-dev] [PATCH v2 0/2] Intel new NIC Boulder Rapid support Michael Qiu
2015-10-26 4:53 ` [dpdk-dev] [PATCH v2 1/2] fm10k: add Intel Boulder Rapid NIC support Michael Qiu
2015-10-26 4:53 ` [dpdk-dev] [PATCH v2 2/2] doc: release note update for Boulder Rapid Support Michael Qiu
2015-10-28 8:29 ` He, Shaopeng [this message]
2015-10-29 22:45 ` [dpdk-dev] [PATCH v2 0/2] Intel new NIC Boulder Rapid support Thomas Monjalon
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=FB82FCC69332B84596FE0CEC3C131094AF94DC@shsmsx102.ccr.corp.intel.com \
--to=shaopeng.he@intel.com \
--cc=dev@dpdk.org \
--cc=michael.qiu@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).