From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org,
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH 2/2] libtracefs: Fix utest compilation
Date: Mon, 21 Jun 2021 11:49:14 +0300 [thread overview]
Message-ID: <20210621084914.336821-2-y.karadz@gmail.com> (raw)
In-Reply-To: <20210621084914.336821-1-y.karadz@gmail.com>
The typo in the name of the API was fixed in a previous patch,
but we need to update the unit tests accordingly.
Fixes: f415871 (libtracefs: Fix typo in function name)
Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com>
---
utest/tracefs-utest.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/utest/tracefs-utest.c b/utest/tracefs-utest.c
index 9186656..a982b1d 100644
--- a/utest/tracefs-utest.c
+++ b/utest/tracefs-utest.c
@@ -729,7 +729,7 @@ static void test_instance_tracing_options(struct tracefs_instance *instance)
CU_TEST(!tracefs_option_is_supported(instance, TRACEFS_OPTION_INVALID));
CU_TEST(!tracefs_option_is_enabled(instance, TRACEFS_OPTION_INVALID));
CU_TEST(tracefs_option_enable(instance, TRACEFS_OPTION_INVALID) == -1);
- CU_TEST(tracefs_option_diasble(instance, TRACEFS_OPTION_INVALID) == -1);
+ CU_TEST(tracefs_option_disable(instance, TRACEFS_OPTION_INVALID) == -1);
name = tracefs_option_name(TRACEFS_OPTION_INVALID);
CU_TEST(!strcmp(name, "unknown"));
/* Test all valid options */
@@ -751,7 +751,7 @@ static void test_instance_tracing_options(struct tracefs_instance *instance)
CU_TEST(check_option(instance, i, true, 1));
CU_TEST(tracefs_option_is_supported(instance, i));
CU_TEST(tracefs_option_is_enabled(instance, i));
- CU_TEST(tracefs_option_diasble(instance, i) == 0);
+ CU_TEST(tracefs_option_disable(instance, i) == 0);
CU_TEST(check_option(instance, i, true, 0));
CU_TEST(tracefs_option_enable(instance, i) == 0);
CU_TEST(check_option(instance, i, true, 1));
@@ -761,7 +761,7 @@ static void test_instance_tracing_options(struct tracefs_instance *instance)
CU_TEST(!tracefs_option_is_enabled(instance, i));
CU_TEST(tracefs_option_enable(instance, i) == 0);
CU_TEST(check_option(instance, i, true, 1));
- CU_TEST(tracefs_option_diasble(instance, i) == 0);
+ CU_TEST(tracefs_option_disable(instance, i) == 0);
CU_TEST(check_option(instance, i, true, 0));
}
}
--
2.27.0
prev parent reply other threads:[~2021-06-21 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 8:49 [PATCH 1/2] libtracefs: Fix typo in documentation Yordan Karadzhov (VMware)
2021-06-21 8:49 ` Yordan Karadzhov (VMware) [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=20210621084914.336821-2-y.karadz@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).