DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
To: david.hunt@intel.com
Cc: anatoly.burakov@intel.com, dev@dpdk.org,
	Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
Subject: [dpdk-dev] [PATCH v2 2/3] test: remove prefix _acpi from UT power function/test names
Date: Wed,  3 Apr 2019 12:32:55 +0200	[thread overview]
Message-ID: <20190403103256.21856-3-lukaszx.krakowiak@intel.com> (raw)
Message-ID: <20190403103255.HjjQewFbEYvAUbY2oToEjrBVoZkem-N_AxIfEH5SBfc@z> (raw)
In-Reply-To: <20190403103256.21856-1-lukaszx.krakowiak@intel.com>

This patch remove prefix _acpi from power UT function/test names.

Signed-off-by: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
---
 app/test/autotest_data.py     |  4 ++--
 app/test/meson.build          |  2 +-
 app/test/test_power_cpufreq.c | 12 ++++++------
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/app/test/autotest_data.py b/app/test/autotest_data.py
index 5f87bb94d..c80801b20 100644
--- a/app/test/autotest_data.py
+++ b/app/test/autotest_data.py
@@ -622,8 +622,8 @@
         "Report":      None,
     },
     {
-        "Name":       "Power ACPI cpufreq autotest",
-        "Command":    "power_acpi_cpufreq_autotest",
+        "Name":       "Power cpufreq autotest",
+        "Command":    "power_cpufreq_autotest",
         "Func":       default_autotest,
         "Report":     None,
     },
diff --git a/app/test/meson.build b/app/test/meson.build
index 4ae3dffea..a389a2b10 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -205,7 +205,7 @@ fast_non_parallel_test_names = [
         'member_autotest',
         'metrics_autotest',
         'pdump_autotest',
-        'power_acpi_cpufreq_autotest',
+        'power_cpufreq_autotest',
         'power_autotest',
         'power_kvm_vm_autotest',
         'reorder_autotest',
diff --git a/app/test/test_power_cpufreq.c b/app/test/test_power_cpufreq.c
index 61b1da05a..d099f2f47 100644
--- a/app/test/test_power_cpufreq.c
+++ b/app/test/test_power_cpufreq.c
@@ -14,14 +14,14 @@
 #ifndef RTE_LIBRTE_POWER
 
 static int
-test_power_acpi_cpufreq(void)
+test_power_cpufreq(void)
 {
 	printf("Power management library not supported, skipping test\n");
 	return TEST_SKIPPED;
 }
 
 static int
-test_power_acpi_caps(void)
+test_power_caps(void)
 {
 	printf("Power management library not supported, skipping test\n");
 	return TEST_SKIPPED;
@@ -367,7 +367,7 @@ check_power_freq_min(void)
 }
 
 static int
-test_power_acpi_cpufreq(void)
+test_power_cpufreq(void)
 {
 	int ret = -1;
 	enum power_management_env env;
@@ -539,7 +539,7 @@ test_power_acpi_cpufreq(void)
 }
 
 static int
-test_power_acpi_caps(void)
+test_power_caps(void)
 {
 	struct rte_power_core_capabilities caps;
 	int ret;
@@ -568,5 +568,5 @@ test_power_acpi_caps(void)
 
 #endif
 
-REGISTER_TEST_COMMAND(power_acpi_cpufreq_autotest, test_power_acpi_cpufreq);
-REGISTER_TEST_COMMAND(power_acpi_caps_autotest, test_power_acpi_caps);
+REGISTER_TEST_COMMAND(power_cpufreq_autotest, test_power_cpufreq);
+REGISTER_TEST_COMMAND(power_caps_autotest, test_power_caps);
-- 
2.19.2.windows.1


  parent reply	other threads:[~2019-04-03 10:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 13:59 [dpdk-dev] [PATCH 0/3] test: improve test coverage for power library Lukasz Krakowiak
2019-03-07 13:59 ` [dpdk-dev] [PATCH 1/3] test: rename test_power_acpi_cpufreq.c -> app/test/test_power_cpufreq.c Lukasz Krakowiak
2019-03-27 15:05   ` Burakov, Anatoly
2019-03-27 15:05     ` Burakov, Anatoly
2019-03-07 13:59 ` [dpdk-dev] [PATCH 2/3] test: remove prefix _acpi from UT power function/test names Lukasz Krakowiak
2019-03-27 15:07   ` Burakov, Anatoly
2019-03-27 15:07     ` Burakov, Anatoly
2019-03-29 22:40     ` Thomas Monjalon
2019-03-29 22:40       ` Thomas Monjalon
2019-03-07 13:59 ` [dpdk-dev] [PATCH 3/3] test: add UT for power turbo feature Lukasz Krakowiak
2019-03-27 15:13   ` Burakov, Anatoly
2019-03-27 15:13     ` Burakov, Anatoly
2019-04-03  9:07     ` Krakowiak, LukaszX
2019-04-03  9:07       ` Krakowiak, LukaszX
2019-04-03 10:01       ` Burakov, Anatoly
2019-04-03 10:01         ` Burakov, Anatoly
2019-04-03 10:32 ` [dpdk-dev] [PATCH v2 0/3] test: improve test coverage for power library Lukasz Krakowiak
2019-04-03 10:32   ` Lukasz Krakowiak
2019-04-03 10:32   ` [dpdk-dev] [PATCH v2 1/3] test: rename test_power_acpi_cpufreq.c -> app/test/test_power_cpufreq.c Lukasz Krakowiak
2019-04-03 10:32     ` Lukasz Krakowiak
2019-04-03 10:32   ` Lukasz Krakowiak [this message]
2019-04-03 10:32     ` [dpdk-dev] [PATCH v2 2/3] test: remove prefix _acpi from UT power function/test names Lukasz Krakowiak
2019-04-15 15:14     ` Hunt, David
2019-04-15 15:14       ` Hunt, David
2019-04-15 15:32     ` Kevin Traynor
2019-04-15 15:32       ` Kevin Traynor
2019-04-03 10:32   ` [dpdk-dev] [PATCH v2 3/3] test: add UT for power turbo feature Lukasz Krakowiak
2019-04-03 10:32     ` Lukasz Krakowiak
2019-04-15 15:22     ` Hunt, David
2019-04-15 15:22       ` Hunt, David
2019-06-07  8:45     ` Hajkowski, MarcinX
2019-04-22 20:42   ` [dpdk-dev] [PATCH v2 0/3] test: improve test coverage for power library Thomas Monjalon
2019-04-22 20:42     ` Thomas Monjalon
2019-07-05  7:35   ` Thomas Monjalon

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=20190403103256.21856-3-lukaszx.krakowiak@intel.com \
    --to=lukaszx.krakowiak@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@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).