test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: Raslan Darawsheh <rasland@mellanox.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "rdarawsheh@asaltech.com" <rdarawsheh@asaltech.com>
Subject: Re: [dts] [PATCH] framework/settings.py should set a driver for	'fortpark' NIC
Date: Mon, 25 Jan 2016 01:31:03 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E13B13DA0@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1453641500-655-2-git-send-email-rasland@mellanox.com>

Applied, thanks Darawsheh. In fact Forpark belonged to Intel Fortville family and its default driver is 'i40e'.

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Raslan Darawsheh
> Sent: Sunday, January 24, 2016 9:18 PM
> To: dts@dpdk.org
> Cc: Raslan Darawsheh; rdarawsheh@asaltech.com
> Subject: [dts] [PATCH] framework/settings.py should set a driver for
> 'fortpark' NIC
> 
> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
> ---
>  framework/settings.py | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/framework/settings.py b/framework/settings.py
> index e5186eb..c3376ce 100644
> --- a/framework/settings.py
> +++ b/framework/settings.py
> @@ -110,6 +110,7 @@ DRIVERS = {
>      'fortville_spirit': 'i40e',
>      'fortville_spirit_single': 'i40e',
>      'redrockcanyou': 'fm10k',
> +    'fortpark':'',
>      'fvl10g_vf':'i40evf',
>      'atwood': 'fm10k',
>      'ConnectX4':'mlx5_core'
> --
> 1.9.1

      reply	other threads:[~2016-01-25  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 13:18 [dts] [PATCH] " Raslan Darawsheh
2016-01-24 13:18 ` [dts] [PATCH] framework/settings.py " Raslan Darawsheh
2016-01-25  1:31   ` 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=86228AFD5BCD8E4EBFD2B90117B5E81E13B13DA0@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --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).