From: Randy Dunlap <rdunlap@infradead.org>
To: Julian Braha <julianbraha@gmail.com>, nathan@kernel.org, nsc@kernel.org
Cc: corbet@lwn.net, skhan@linuxfoundation.org,
mchehab+huawei@kernel.org, jani.nikula@intel.com, tj@kernel.org,
grahamr@qti.qualcomm.com, officialnaumansabir@gmail.com,
nico@fluxnic.net, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: add a history of the Kconfig language
Date: Tue, 3 Nov 2026 16:49:06 -0800 [thread overview]
Message-ID: <d235a1f4-9bd1-4d28-ad6e-bcf1d4529c5b@infradead.org> (raw)
In-Reply-To: <20261103190832.3861337-1-julianbraha@gmail.com>
Hi,
On 11/3/26 11:08 AM, Julian Braha wrote:
> +6.18
> +----
> +
> +**Syntax and semantics**:
> +
> +- add ``transitional`` to specify that an option should no longer be written to
> + the output ``.config`` file. (f9afce4f32e9 and 0902b3cb23ce)
FWIW, this also replaces using
depends on OPTION1 {<=, >=} OPTION2
that has been used/preferred in a few instances.
./fs/cramfs/Kconfig: depends on CRAMFS && CRAMFS <= MTD
./drivers/acpi/apei/Kconfig: depends on CXL_BUS && CXL_BUS <= ACPI_APEI_EINJ
./drivers/net/ethernet/sfc/Kconfig: depends on SFC && CXL_MEM >= SFC
./drivers/cxl/Kconfig: depends on EDAC >= CXL_BUS
./security/keys/trusted-keys/Kconfig: depends on TCG_TPM >= TRUSTED_KEYS
./security/keys/trusted-keys/Kconfig: depends on TEE >= TRUSTED_KEYS
./security/keys/trusted-keys/Kconfig: depends on CRYPTO_DEV_FSL_CAAM_JR >= TRUSTED_KEYS
./security/keys/trusted-keys/Kconfig: depends on CRYPTO_DEV_MXS_DCP >= TRUSTED_KEYS
./security/keys/trusted-keys/Kconfig: depends on PSERIES_PLPKS >= TRUSTED_KEYS
--
~Randy
next prev parent reply other threads:[~2026-11-04 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 19:08 Julian Braha
2026-11-04 0:49 ` Randy Dunlap [this message]
2026-11-04 0:49 ` Randy Dunlap
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=d235a1f4-9bd1-4d28-ad6e-bcf1d4529c5b@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=grahamr@qti.qualcomm.com \
--cc=jani.nikula@intel.com \
--cc=julianbraha@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nathan@kernel.org \
--cc=nico@fluxnic.net \
--cc=nsc@kernel.org \
--cc=officialnaumansabir@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=tj@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
all inboxes | Powered by JetHome®