All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] selftests/nolibc: drop custom EXTRACONFIG functionality
Date: Sat, 1 Feb 2025 11:13:05 +0100	[thread overview]
Message-ID: <20250201101305.GD5849@1wt.eu> (raw)
In-Reply-To: <20250123-nolibc-config-v2-1-5701c35995d6@weissschuh.net>

On Thu, Jan 23, 2025 at 08:37:37AM +0100, Thomas Weißschuh wrote:
> kbuild already contains logic to merge predefines snippets into a
> defconfig file. This already works nicely with the current "defconfig"
> target. Make use of the snippet and drop the custom logic.
> 
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
>  tools/testing/selftests/nolibc/Makefile | 9 +--------
>  1 file changed, 1 insertion(+), 8 deletions(-)
> 
> diff --git a/tools/testing/selftests/nolibc/Makefile b/tools/testing/selftests/nolibc/Makefile
> index 7d14a7c0cb62608f328b251495264517d333db2e..ba044c8a042ce345ff90bdd35569de4b5acd117d 100644
> --- a/tools/testing/selftests/nolibc/Makefile
> +++ b/tools/testing/selftests/nolibc/Makefile
> @@ -82,7 +82,7 @@ DEFCONFIG_x86        = defconfig
>  DEFCONFIG_arm64      = defconfig
>  DEFCONFIG_arm        = multi_v7_defconfig
>  DEFCONFIG_mips32le   = malta_defconfig
> -DEFCONFIG_mips32be   = malta_defconfig
> +DEFCONFIG_mips32be   = malta_defconfig generic/eb.config
>  DEFCONFIG_ppc        = pmac32_defconfig
>  DEFCONFIG_ppc64      = powernv_be_defconfig
>  DEFCONFIG_ppc64le    = powernv_defconfig
> @@ -93,9 +93,6 @@ DEFCONFIG_s390       = defconfig
>  DEFCONFIG_loongarch  = defconfig
>  DEFCONFIG            = $(DEFCONFIG_$(XARCH))
>  
> -EXTRACONFIG_mips32be = -d CONFIG_CPU_LITTLE_ENDIAN -e CONFIG_CPU_BIG_ENDIAN
> -EXTRACONFIG           = $(EXTRACONFIG_$(XARCH))
> -
>  # optional tests to run (default = all)
>  TEST =
>  
> @@ -265,10 +262,6 @@ 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) olddefconfig < /dev/null; \
> -	fi

OK it's no longer needed thanks to your change above, but to we really
want to get rid of that feature allowing anyone to add their own extra
config ? I'm not sure. For example maybe the current build script helps
on bare metal, when trying to add support for new archs or other features
not yet in defconfig ? We could leave EXTRACONFIG_* empty by default and
user-defined, as I don't feel like it blocks anything to keep it.

Just my two cents, 
Willy

  reply	other threads:[~2025-02-01 10:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23  7:37 [PATCH v2 0/5] selftests/nolibc: test kernel configuration cleanups Thomas Weißschuh
2025-01-23  7:37 ` [PATCH v2 1/5] selftests/nolibc: drop custom EXTRACONFIG functionality Thomas Weißschuh
2025-02-01 10:13   ` Willy Tarreau [this message]
2025-02-01 10:17     ` Thomas Weißschuh
2025-02-01 10:20       ` Willy Tarreau
2025-01-23  7:37 ` [PATCH v2 2/5] selftests/nolibc: drop call to prepare target Thomas Weißschuh
2025-02-01 10:03   ` Willy Tarreau
2025-01-23  7:37 ` [PATCH v2 3/5] selftests/nolibc: drop call to mrproper target Thomas Weißschuh
2025-02-01 10:07   ` Willy Tarreau
2025-01-23  7:37 ` [PATCH v2 4/5] selftests/nolibc: execute defconfig before other targets Thomas Weißschuh
2025-02-01 10:09   ` Willy Tarreau
2025-01-23  7:37 ` [PATCH v2 5/5] selftests/nolibc: always keep test kernel configuration up to date Thomas Weißschuh
2025-02-01 10:13   ` 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=20250201101305.GD5849@1wt.eu \
    --to=w@1wt.eu \
    --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.