From: "Liu, Yong" <yong.liu@intel.com>
To: Ali Alnubani <alialnu@mellanox.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH for-next v3 0/3] nic_single_core_perf: add support for Mellanox's nics
Date: Mon, 02 Apr 2018 20:57:15 +0800 [thread overview]
Message-ID: <5AC228AB.10009@intel.com> (raw)
In-Reply-To: <20180330225241.1399-1-alialnu@mellanox.com>
Thanks Ali, applied into next branch.
On 03/31/2018 06:52 AM, Ali Alnubani wrote:
> This patchset adds support to run nic_single_core_perf test on
> ConnectX-5 EX, ConnectX-4 LX 25G, and ConnectX-4 LX 40G.
prev parent reply other threads:[~2018-04-02 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 22:52 Ali Alnubani
2018-03-30 22:52 ` [dts] [PATCH for-next v3 1/3] framework/project_dpdk: pass module setup for mlx5_core Ali Alnubani
2018-03-30 22:52 ` [dts] [PATCH for-next v3 2/3] nics/net_device: add a function to get nic speed Ali Alnubani
2018-03-30 22:52 ` [dts] [PATCH for-next v3 3/3] nic_single_core_perf: add support for Mellanox's nics Ali Alnubani
2018-04-02 12:57 ` Liu, Yong [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=5AC228AB.10009@intel.com \
--to=yong.liu@intel.com \
--cc=alialnu@mellanox.com \
--cc=dts@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).