From: Kees Cook <kees@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Masahiro Yamada <masahiroy@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>,
Stephen Brennan <stephen.s.brennan@oracle.com>,
Marco Bonelli <marco@mebeim.net>, Petr Vorel <pvorel@suse.cz>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] kconfig: Add transitional symbol attribute for migration support
Date: Mon, 1 Sep 2025 09:45:44 -0700 [thread overview]
Message-ID: <202509010944.CAAFB2ED22@keescook> (raw)
In-Reply-To: <a123ab8b-a335-48a1-9ac3-e3b348d78cd1@infradead.org>
On Mon, Sep 01, 2025 at 09:39:46AM -0700, Randy Dunlap wrote:
> Are you (implicitly?) saying that all previous attempts at transitional
> kconfig symbols have failed? If so, I just wasn't aware of that.
I haven't found any way to do a "proper" CONFIG transition. I looked
through past transitions and they all left stuff visible. Is there a way
to actually do this with existing kconfig?
--
Kees Cook
next prev parent reply other threads:[~2025-09-01 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 2:01 [PATCH v2] kconfig: Add transitional symbol attribute for migration support Kees Cook
2025-09-01 8:34 ` Vegard Nossum
2025-09-01 16:56 ` Kees Cook
2025-09-01 18:20 ` Vegard Nossum
2025-09-01 18:31 ` Kees Cook
2025-09-01 18:44 ` Vegard Nossum
2025-09-04 2:51 ` Kees Cook
2025-09-04 17:03 ` Vegard Nossum
2025-09-04 17:10 ` Vegard Nossum
2025-09-05 9:41 ` Vegard Nossum
2025-09-05 16:24 ` Kees Cook
2025-09-05 16:23 ` Kees Cook
2025-09-23 21:36 ` Kees Cook
2025-09-01 9:09 ` Jani Nikula
2025-09-01 16:48 ` Kees Cook
2025-09-01 16:39 ` Randy Dunlap
2025-09-01 16:45 ` Kees Cook [this message]
2025-09-01 16:54 ` 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=202509010944.CAAFB2ED22@keescook \
--to=kees@kernel.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco@mebeim.net \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=ojeda@kernel.org \
--cc=pvorel@suse.cz \
--cc=rdunlap@infradead.org \
--cc=stephen.s.brennan@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.