test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yong Liu <yong.liu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH 3/6] framework test_case: add kernel driver variable
Date: Wed,  3 Feb 2016 14:50:14 +0800	[thread overview]
Message-ID: <1454482217-25147-4-git-send-email-yong.liu@intel.com> (raw)
In-Reply-To: <1454482217-25147-1-git-send-email-yong.liu@intel.com>

Add kernel module name in test case module, most times nics in same family
belong to same kernel driver. With this variable, test case can handle
difference between NICs more easily.

Signed-off-by: Marvin Liu <yong.liu@intel.com>

diff --git a/framework/test_case.py b/framework/test_case.py
index f601381..9ef1c32 100644
--- a/framework/test_case.py
+++ b/framework/test_case.py
@@ -53,6 +53,7 @@ class TestCase(object):
             self.nic = self.nics[0]
         else:
             self.nic = ''
+        self.kdriver = self.get_nic_driver(self.nic)
 
     def set_up_all(self):
         pass
@@ -74,7 +75,7 @@ class TestCase(object):
         if nic_name in DRIVERS.keys():
             return DRIVERS[nic_name]
 
-        raise ValueError(nic_name)
+        return "Unknown"
 
     def get_nic_name(self, pci_id):
         for nic_name, pci in NICS.items():
-- 
1.9.3

  parent reply	other threads:[~2016-02-03  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03  6:50 [dts] [PATCH 0/6] Support Boulder Rapid Yong Liu
2016-02-03  6:50 ` [dts] [PATCH 1/6] nics fm10k: rename fm10k module to rrc Yong Liu
2016-02-03  6:50 ` [dts] [PATCH 2/6] framework settings: support boulderrapid nic Yong Liu
2016-02-03  6:50 ` Yong Liu [this message]
2016-02-03  6:50 ` [dts] [PATCH 4/6] nics: add support for Boulder Rapid Yong Liu
2016-02-03  6:50 ` [dts] [PATCH 5/6] nics net_device: support Boulder Rapid network object Yong Liu
2016-02-03  6:50 ` [dts] [PATCH 6/6] tests: support Boulder Rapid Yong Liu

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=1454482217-25147-4-git-send-email-yong.liu@intel.com \
    --to=yong.liu@intel.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).