From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>, Zhangjin Wu <falcon@tinylab.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 5/6] selftests/nolibc: extraconfig support
Date: Sun, 5 Nov 2023 11:35:40 +0100 [thread overview]
Message-ID: <ZUdv/AniaMBC2KFW@1wt.eu> (raw)
In-Reply-To: <20231105-nolibc-mips-be-v1-5-6c2ad3e50a1f@weissschuh.net>
On Sun, Nov 05, 2023 at 11:09:59AM +0100, Thomas Weißschuh wrote:
> Allow some postprocessing of defconfig files.
>
> Suggested-by: Zhangjin Wu <falcon@tinylab.org>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> tools/testing/selftests/nolibc/Makefile | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/testing/selftests/nolibc/Makefile b/tools/testing/selftests/nolibc/Makefile
> index f8fea9fa0263..02c074e73a28 100644
> --- a/tools/testing/selftests/nolibc/Makefile
> +++ b/tools/testing/selftests/nolibc/Makefile
> @@ -81,6 +81,8 @@ DEFCONFIG_s390 = defconfig
> DEFCONFIG_loongarch = defconfig
> DEFCONFIG = $(DEFCONFIG_$(XARCH))
>
> +EXTRACONFIG = $(EXTRACONFIG_$(XARCH))
> +
> # optional tests to run (default = all)
> TEST =
>
> @@ -227,6 +229,10 @@ initramfs: nolibc-test
>
> defconfig:
> $(Q)$(MAKE) -C $(srctree) ARCH=$(ARCH) CC=$(CC) CROSS_COMPILE=$(CROSS_COMPILE) mrproper $(DEFCONFIG) prepare
> + $(Q)if [ -n "$(EXTRACONFIG)" ]; then \
> + $(srctree)/scripts/config --file $(objtree)/.config $(EXTRACONFIG); \
> + $(MAKE) -C $(srctree) ARCH=$(ARCH) CC=$(CC) CROSS_COMPILE=$(CROSS_COMPILE) oldconfig < /dev/null; \
You should instead use "olddefconfig" for this. It reuses defconfig but
uses defaults for new questions. I've already experienced issues from
time to time using /dev/null with oldconfig as you did above, with a
process looping forever (probably on a non acceptable choice I guess),
and never met such issues anymore since I switched to olddefconfig
instead.
Willy
next prev parent reply other threads:[~2023-11-05 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 10:09 [PATCH 0/6] tools/nolibc: MIPS bugfixes and refactoring Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 1/6] tools/nolibc: error out on unsupported architecture Thomas Weißschuh
2023-11-05 10:36 ` Willy Tarreau
2023-11-05 10:09 ` [PATCH 2/6] tools/nolibc: move MIPS ABI validation into arch-mips.h Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 3/6] selftests/nolibc: use XARCH for MIPS Thomas Weißschuh
2023-11-05 10:32 ` Willy Tarreau
2023-11-05 10:49 ` Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 4/6] selftests/nolibc: explicitly specify ABI " Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 5/6] selftests/nolibc: extraconfig support Thomas Weißschuh
2023-11-05 10:35 ` Willy Tarreau [this message]
2023-11-05 10:10 ` [PATCH 6/6] selftests/nolibc: add configuration for mipso32be Thomas Weißschuh
2023-11-05 10:37 ` [PATCH 0/6] tools/nolibc: MIPS bugfixes and refactoring Willy Tarreau
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=ZUdv/AniaMBC2KFW@1wt.eu \
--to=w@1wt.eu \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@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 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.