From: James Clark <james.clark@linaro.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
linux-kernel@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] stm class: Fix Kconfig symbols
Date: Mon, 19 Jan 2026 16:32:18 +0000 [thread overview]
Message-ID: <641fad10-e693-43ae-a278-1bf70d56b6d3@linaro.org> (raw)
In-Reply-To: <20260119154606.GE2732125@e132581.arm.com>
On 19/01/2026 3:46 pm, Leo Yan wrote:
> On Mon, Jan 19, 2026 at 12:35:23PM +0000, James Clark wrote:
>
> [...]
>
>>> @@ -28,7 +28,7 @@ config STM_PROTO_BASIC
>>> config STM_PROTO_SYS_T
>>> tristate "MIPI SyS-T STM framing protocol driver"
>>> - default CONFIG_STM
>>> + default STM
>>
>> The help below here says "If you don't know what this is, say N." which
>> makes me wonder if this should be on by default or not?
>
> STM_PROTO_BASIC is a must have config when enabling STM. While
> STM_PROTO_SYS_T is not mandatory, but it is useful to build it so that
> users can select the protocol dynamically at runtime.
>
Should probably change that text to say "If you don't know what this is,
say Y" then? Otherwise it makes the default-on look like a mistake.
>> Also everything is in an "if STM" block, so "default STM" is a bit
>> redundant. It's not that obvious what the intention was.
>
> They are two different things.
>
> "if STM" expresses a dependency (the module depends on STM), while
> "default STM" means the module will be selected by default if STM is
> enabled.
>
Yeah they're the same, it was just a minor nit that "if STM, depends on
STM" seemed redundant (and obviously more error prone). "default y"
would also be the same and not repeat the same thing twice. Don't think
it matters too much either way.
> Thanks,
> Leo
>
> P.s. I also tried using the "select" and "imply" syntax to enable the
> protocol configurations. Based on testing, I did not observe any
> difference compared to using the "default" syntax.
prev parent reply other threads:[~2026-01-19 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 9:39 Leo Yan
2026-01-19 11:22 ` Leo Yan
2026-01-19 12:35 ` James Clark
2026-01-19 15:46 ` Leo Yan
2026-01-19 16:32 ` James Clark [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=641fad10-e693-43ae-a278-1bf70d56b6d3@linaro.org \
--to=james.clark@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=coresight@lists.linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
/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
all inboxes | Powered by JetHome®