From: Julian Braha <julianbraha@gmail.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>,
mturquette@baylibre.com, sboyd@kernel.org, bmasney@redhat.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v6 3/3] clk: cs2600: Add KUnit test for CS2600 driver
Date: Thu, 2 Jul 2026 20:24:27 +0100 [thread overview]
Message-ID: <2723c6d5-7a3e-436b-9ac2-12e5b0a3d1c5@gmail.com> (raw)
In-Reply-To: <20260630155549.824059-4-rf@opensource.cirrus.com>
Hi Richard,
On 6/30/26 16:55, Richard Fitzgerald wrote:
> +++ b/drivers/clk/cirrus/Kconfig
> @@ -8,3 +8,16 @@ config COMMON_CLK_CS2600
> help
> If you say yes here you get support for the CS2600 clock synthesizer
> and multiplier.
> +
> +config COMMON_CLK_CS2600_KUNIT_TEST
> + tristate "KUnit test for CS2600 clock driver" if !KUNIT_ALL_TESTS
> + depends on COMMON_CLK_CS2600
> + depends on KUNIT
> + depends on REGULATOR
> + depends on REGULATOR_FIXED_VOLTAGE
> + default KUNIT_ALL_TESTS
> + help
> + Build the KUnit tests for the Cirrus Logic CS2600
> + clock driver.
> +
> + If unsure say N.
Could you format your kconfig help text with a tab + 2 spaces, as the
kconfig documentation shows in its example?
In fact, your previous patch in this series (adding COMMON_CLK_CS2600)
formatted it correctly.
- Julian Braha
prev parent reply other threads:[~2026-07-02 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 15:55 [PATCH v6 0/3] Cirrus Logic CS2600 clock device Richard Fitzgerald
2026-06-30 15:55 ` [PATCH v6 1/3] dt-bindings: clock: cs2600: Add support for the CS2600 Richard Fitzgerald
2026-07-01 6:48 ` Krzysztof Kozlowski
2026-07-01 8:59 ` Richard Fitzgerald
2026-06-30 15:55 ` [PATCH v6 2/3] clk: cs2600: Add Fractional-N clock driver Richard Fitzgerald
2026-06-30 16:59 ` Uwe Kleine-König
2026-06-30 15:55 ` [PATCH v6 3/3] clk: cs2600: Add KUnit test for CS2600 driver Richard Fitzgerald
2026-07-02 19:24 ` Julian Braha [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=2723c6d5-7a3e-436b-9ac2-12e5b0a3d1c5@gmail.com \
--to=julianbraha@gmail.com \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=robh@kernel.org \
--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