From: Brian Masney <bmasney@redhat.com>
To: sboyd@kernel.org
Cc: mturquette@baylibre.com, mripard@kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] clk: test: remove kunit_skip() for divider tests that have been fixed
Date: Tue, 20 May 2025 15:28:46 -0400 [thread overview]
Message-ID: <20250520192846.9614-3-bmasney@redhat.com> (raw)
In-Reply-To: <20250520192846.9614-1-bmasney@redhat.com>
These issues have been fixed in the clk core, so let's remove the
kunit_skip().
Signed-off-by: Brian Masney <bmasney@redhat.com>
---
drivers/clk/clk_test.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/clk/clk_test.c b/drivers/clk/clk_test.c
index e6df1d2274b2..3f0bc44c06fd 100644
--- a/drivers/clk/clk_test.c
+++ b/drivers/clk/clk_test.c
@@ -788,8 +788,6 @@ static void clk_test_rate_change_sibling_div_div_2(struct kunit *test)
struct clk_rate_change_sibling_div_div_context *ctx = test->priv;
int ret;
- kunit_skip(test, "This needs to be fixed in the core.");
-
ret = clk_set_rate(ctx->child1_clk, DUMMY_CLOCK_RATE_48_MHZ);
KUNIT_ASSERT_EQ(test, ret, 0);
@@ -808,8 +806,6 @@ static void clk_test_rate_change_sibling_div_div_3(struct kunit *test)
struct clk_rate_change_sibling_div_div_context *ctx = test->priv;
int ret;
- kunit_skip(test, "This needs to be fixed in the core.");
-
ret = clk_set_rate(ctx->child1_clk, DUMMY_CLOCK_RATE_16_MHZ);
KUNIT_ASSERT_EQ(test, ret, 0);
--
2.49.0
next prev parent reply other threads:[~2025-05-20 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 19:28 [PATCH 0/2] clk: preserve original rate when a sibling clk changes it's rate Brian Masney
2025-05-20 19:28 ` [PATCH 1/2] " Brian Masney
2025-05-27 12:36 ` Maxime Ripard
2025-05-27 19:07 ` Brian Masney
2025-05-20 19:28 ` Brian Masney [this message]
2025-05-28 23:23 ` [PATCH 0/2] " Brian Masney
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=20250520192846.9614-3-bmasney@redhat.com \
--to=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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