From: Maxime Ripard <maxime@cerno.tech>
Date: Fri, 1 Apr 2022 12:53:49 +0000 (+0200)
Subject: clk: tests: Add reference to the orphan mux bug report
X-Git-Tag: accepted/tizen/unified/20230118.172025~677
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=927aa200f5f2d69381e044b9636897ea16d4e631;p=platform%2Fkernel%2Flinux-rpi.git

clk: tests: Add reference to the orphan mux bug report

Some more context might be useful for unit-tests covering a previously
reported bug, so let's add a link to the discussion for that bug.

Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com> # imx8mp
Tested-by: Marek Szyprowski <m.szyprowski@samsung.com> # exynos4210, meson g12b
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
---

diff --git a/drivers/clk/clk_test.c b/drivers/clk/clk_test.c
index 4e4428f..77230cc 100644
--- a/drivers/clk/clk_test.c
+++ b/drivers/clk/clk_test.c
@@ -314,6 +314,9 @@ static void clk_orphan_transparent_single_parent_mux_test_exit(struct kunit *tes
 /*
  * Test that a mux-only clock, with an initial rate within a range,
  * will still have the same rate after the range has been enforced.
+ *
+ * See:
+ * https://lore.kernel.org/linux-clk/7720158d-10a7-a17b-73a4-a8615c9c6d5c@collabora.com/
  */
 static void clk_test_orphan_transparent_parent_mux_set_range(struct kunit *test)
 {