test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Qiu, Michael" <michael.qiu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] framework: Add Intel new NIC support
Date: Thu, 12 Feb 2015 00:57:06 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10D7ADB0@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1423658616-14903-1-git-send-email-michael.qiu@intel.com>

Applied, thanks Michael.

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Michael Qiu
> Sent: Wednesday, February 11, 2015 8:44 PM
> To: dts@dpdk.org
> Subject: [dts] [PATCH] framework: Add Intel new NIC support
> 
> Red Rock Canyou is one new NIC of Intel, kernel driver is named
> fm10k.
> 
> This patch only add base support for this NIC, so that the framework
> can identify this NIC.
> 
> Signed-off-by: Michael Qiu <michael.qiu@intel.com>
> ---
>  framework/settings.py | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/framework/settings.py b/framework/settings.py
> index 23b5788..ba9b5f5 100644
> --- a/framework/settings.py
> +++ b/framework/settings.py
> @@ -58,7 +58,7 @@ NICS = {
>      'fortville_eagle': '8086:1572',
>      'fortville_spirit': '8086:1583',
>      'fortville_spirit_single': '8086:1584',
> -    'rubyrappid': '8086:15a4',
> +    'redrockcanyou': '8086:15a4',
>  }
> 
>  DRIVERS = {
> @@ -87,7 +87,7 @@ DRIVERS = {
>      'fortville_eagle': 'i40e',
>      'fortville_spirit': 'i40e',
>      'fortville_spirit_single':'i40e',
> -    'rubyrappid': 'fm10k',
> +    'redrockcanyou': 'fm10k',
>  }
> 
>  """
> --
> 1.9.3

      reply	other threads:[~2015-02-12  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 12:43 Michael Qiu
2015-02-12  0: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=86228AFD5BCD8E4EBFD2B90117B5E81E10D7ADB0@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@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).