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 3/4] kconfig: tests: warn_changed_input: Simplify by reusing the extra env
Date: Sat, 19 Sep 2026 18:57:59 +0100 [thread overview]
Message-ID: <0bf09003-b6ed-48de-a826-9d978f3edb70@gmail.com> (raw)
In-Reply-To: <20260917-kconfig-tests-minor-updates-v1-3-286e5c985244@fritz.com>
On 9/17/26 14:38, Nicolas Schier wrote:
> Define the extra environment once and re-use it for the respective
> _run_conf() calls to increase readability.
>
> Signed-off-by: Nicolas Schier <n.schier@fritz.com>
Reviewed-by: Julian Braha <julianbraha@gmail.com>
next prev parent reply other threads:[~2026-09-19 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 13:38 [PATCH 0/4] kconfig: tests: Minor fixes and cleanups for warn_changed_input Nicolas Schier
2026-09-17 13:38 ` [PATCH 1/4] kconfig: tests: Reset KCONFIG_WARN_CHANGED_INPUT by default Nicolas Schier
2026-09-19 17:29 ` Julian Braha
2026-09-24 7:35 ` Nicolas Schier
2026-09-25 20:00 ` Nathan Chancellor
2026-09-25 22:19 ` Julian Braha
2026-09-17 13:38 ` [PATCH 2/4] kconfig: tests: Provide defconfig outfile for savedefconfig Nicolas Schier
2026-09-19 17:45 ` Julian Braha
2026-09-24 8:31 ` Nicolas Schier
2026-09-17 13:38 ` [PATCH 3/4] kconfig: tests: warn_changed_input: Simplify by reusing the extra env Nicolas Schier
2026-09-19 17:57 ` Julian Braha [this message]
2026-09-17 13:38 ` [PATCH 4/4] kconfig: tests: {old,save}defconfig: Forward dynamic keyword arguments Nicolas Schier
2026-09-19 18:09 ` Julian Braha
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=0bf09003-b6ed-48de-a826-9d978f3edb70@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.