diff options
author | Maxime Ripard <[email protected]> | 2022-08-16 13:25:12 +0200 |
---|---|---|
committer | Stephen Boyd <[email protected]> | 2022-09-15 09:30:43 -0700 |
commit | 7d79c26b60e623a9a089d771f81c5997bda577cd (patch) | |
tree | 8ea262efcfdd13c37748a1bf4ee55c89c526c190 | |
parent | 090962b6a90a2bf81142f6d5da9492380d5fba08 (diff) |
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 <[email protected]> # imx8mp
Tested-by: Marek Szyprowski <[email protected]> # exynos4210, meson g12b
Signed-off-by: Maxime Ripard <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Tested-by: Linux Kernel Functional Testing <[email protected]>
Tested-by: Naresh Kamboju <[email protected]>
Signed-off-by: Stephen Boyd <[email protected]>
-rw-r--r-- | drivers/clk/clk_test.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/clk/clk_test.c b/drivers/clk/clk_test.c index 1a7cb482ec58..b8e32406a6e4 100644 --- a/drivers/clk/clk_test.c +++ b/drivers/clk/clk_test.c @@ -322,6 +322,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/[email protected]/ */ static void clk_test_orphan_transparent_parent_mux_set_range(struct kunit *test) { |