From: Julian Braha <julianbraha@gmail.com>
To: Nicolas Schier <n.schier@fritz.com>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
Pengpeng Hou <pengpeng@iscas.ac.cn>,
Ulf Magnusson <ulfalizer@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] kconfig: tests: Reset all KCONFIG_* env variables by default
Date: Tue, 29 Sep 2026 22:14:25 +0100 [thread overview]
Message-ID: <f3a26a6d-e2ea-4d84-9e3f-fa8e0d891728@gmail.com> (raw)
In-Reply-To: <20260929-kconfig-tests-minor-updates-v2-1-c5902bee1d0c@fritz.com>
On 9/29/26 08:59, Nicolas Schier wrote:
> Reset all environment variables with names starting with 'KCONFIG_' from
> the user-provided environment.
>
> This fixes the 'warn_changed_input' test on systems with
> KCONFIG_WARN_CHANGED_INPUT=1 and ensures a cleaner test environment.
>
> Fixes: 645323a7f4e5 ("kconfig: add optional warnings for changed input values")
> Signed-off-by: Nicolas Schier <n.schier@fritz.com>
Reviewed-by: Julian Braha <julianbraha@gmail.com>
next prev parent reply other threads:[~2026-09-29 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 7:59 [PATCH v2 0/4] kconfig: tests: Minor fixes and cleanups for warn_changed_input Nicolas Schier
2026-09-29 7:59 ` [PATCH v2 1/4] kconfig: tests: Reset all KCONFIG_* env variables by default Nicolas Schier
2026-09-29 21:14 ` Julian Braha [this message]
2026-09-29 7:59 ` [PATCH v2 2/4] kconfig: tests: Provide defconfig outfile for savedefconfig Nicolas Schier
2026-09-29 7:59 ` [PATCH v2 3/4] kconfig: tests: warn_changed_input: Simplify by reusing the extra env Nicolas Schier
2026-09-29 7:59 ` [PATCH v2 4/4] kconfig: tests: {old,save}defconfig: Forward dynamic keyword arguments Nicolas Schier
2026-09-30 13:47 ` [PATCH v2 0/4] kconfig: tests: Minor fixes and cleanups for warn_changed_input Nathan Chancellor
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=f3a26a6d-e2ea-4d84-9e3f-fa8e0d891728@gmail.com \
--to=julianbraha@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n.schier@fritz.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=pengpeng@iscas.ac.cn \
--cc=ulfalizer@gmail.com \
--cc=yamada.masahiro@socionext.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.