From: "Liu, Yong" <yong.liu@intel.com>
To: Raslan Darawsheh <rasland@mellanox.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "fhamad@asaltech.com" <fhamad@asaltech.com>,
"olgas@mellanox.com" <olgas@mellanox.com>,
"rdarawsheh@asaltech.com" <rdarawsheh@asaltech.com>
Subject: Re: [dts] [PATCH 0/3] supporting Mellanox ConnectX4 NIC in DTS
Date: Thu, 21 Jan 2016 14:26:41 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E13B128D9@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1453378680-3240-1-git-send-email-rasland@mellanox.com>
Applied. Thanks, Darawsheh.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Raslan Darawsheh
> Sent: Thursday, January 21, 2016 8:18 PM
> To: dts@dpdk.org
> Cc: fhamad@asaltech.com; olgas@mellanox.com; Raslan Darawsheh;
> rdarawsheh@asaltech.com
> Subject: [dts] [PATCH 0/3] supporting Mellanox ConnectX4 NIC in DTS
>
> the following patches where to support Mellanox ConnectX4 NIC in the DTS
> tests
>
> Raslan Darawsheh (3):
> framework/settings.py adding support for ConnectX4 NIC
> framework/project_dpdk.py enabling MLX5 PMD for Mellanox NIC
> executions/execution.* adding mlx5_core to bind Mellanox NIC's to the
> driver
>
> executions/execution.cfg | 2 +-
> executions/execution_FVL.cfg | 2 +-
> executions/execution_smoke.cfg | 2 +-
> framework/project_dpdk.py | 6 ++++++
> framework/settings.py | 6 ++++--
> 5 files changed, 13 insertions(+), 5 deletions(-)
>
> --
> 1.9.1
prev parent reply other threads:[~2016-01-21 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 12:17 Raslan Darawsheh
2016-01-21 12:17 ` [dts] [PATCH 1/3] framework/settings.py adding support for ConnectX4 NIC Raslan Darawsheh
2016-01-21 12:17 ` [dts] [PATCH 2/3] framework/project_dpdk.py enabling MLX5 PMD for Mellanox NIC Raslan Darawsheh
2016-01-21 12:18 ` [dts] [PATCH 3/3] executions/execution.* adding mlx5_core to bind Mellanox NIC's to the driver Raslan Darawsheh
2016-01-21 14:26 ` 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=86228AFD5BCD8E4EBFD2B90117B5E81E13B128D9@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=fhamad@asaltech.com \
--cc=olgas@mellanox.com \
--cc=rasland@mellanox.com \
--cc=rdarawsheh@asaltech.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).