From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V1 1/2] tests/kni: fix typo in output message
Date: Wed, 10 Jul 2019 11:09:21 +0800 [thread overview]
Message-ID: <1562728162-214888-2-git-send-email-yufengx.mo@intel.com> (raw)
In-Reply-To: <1562728162-214888-1-git-send-email-yufengx.mo@intel.com>
fix typo issue in output message.
Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
tests/TestSuite_kni.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_kni.py b/tests/TestSuite_kni.py
index cf2403d..f1f85df 100644
--- a/tests/TestSuite_kni.py
+++ b/tests/TestSuite_kni.py
@@ -780,7 +780,7 @@ class TestKni(TestCase):
total_cores = len(self.config['tx_cores'] + self.config[
'rx_cores'] + self.config['kernel_cores'])
if total_cores > self.dut_physical_cores():
- self.logger.info("Skiping step %s (%d cores needed, got %d)" %
+ self.logger.info("Skipping step %s (%d cores needed, got %d)" %
(step['config'], total_cores,
self.dut_physical_cores())
)
@@ -850,7 +850,7 @@ class TestKni(TestCase):
total_cores = len(self.config['tx_cores'] + self.config[
'rx_cores'] + self.config['kernel_cores'])
if total_cores > self.dut_physical_cores():
- self.logger.info("Skiping step %s (%d cores needed, got %d)" %
+ self.logger.info("Skipping step %s (%d cores needed, got %d)" %
(step['config'], total_cores,
self.dut_physical_cores())
)
--
1.9.3
next prev parent reply other threads:[~2019-07-10 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 3:09 [dts] [PATCH V1 0/2] dts/tests: " yufengmx
2019-07-10 3:09 ` yufengmx [this message]
2019-07-10 8:28 ` [dts] [PATCH V1 1/2] tests/kni: " Yao, Lei A
2019-07-10 3:09 ` [dts] [PATCH V1 2/2] tests/vm_power_manager: " yufengmx
2019-07-10 8:31 ` Yao, Lei A
2019-08-06 10:08 ` Tu, Lijuan
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=1562728162-214888-2-git-send-email-yufengx.mo@intel.com \
--to=yufengx.mo@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).