From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/nolibc: fix sparc32 tests with -mcpu=v9
Date: Tue, 6 Jan 2026 12:47:56 +0100 [thread overview]
Message-ID: <18bb48f2-b5aa-42a6-bc09-4773e1907670@t-8ch.de> (raw)
In-Reply-To: <CAMuHMdUHBm_oiyeUumRc=avp+QCiCLZAfi0BvLwToAM3TumGmQ@mail.gmail.com>
Hi Geert,
On 2026-01-06 12:40:12+0100, Geert Uytterhoeven wrote:
> On Sun, 4 Jan 2026 at 23:14, Thomas Weißschuh <linux@weissschuh.net> wrote:
(...)
> > --- a/tools/testing/selftests/nolibc/Makefile.nolibc
> > +++ b/tools/testing/selftests/nolibc/Makefile.nolibc
> > @@ -117,7 +117,7 @@ DEFCONFIG_riscv32 = rv32_defconfig
> > DEFCONFIG_riscv64 = defconfig
> > DEFCONFIG_s390x = defconfig
> > DEFCONFIG_loongarch = defconfig
> > -DEFCONFIG_sparc32 = sparc32_defconfig
> > +DEFCONFIG_sparc32 = sparc64_defconfig
>
> How can we test sparc32 using a 64-bit kernel?
CONFIG_COMPAT=y
Please note that this changed in (the now committed) v2 anyways:
https://lore.kernel.org/lkml/20260106-nolibc-sparc32-fix-v2-1-7c5cd6b175c2@weissschuh.net/
> > DEFCONFIG_sparc64 = sparc64_defconfig
> > DEFCONFIG_m68k = virt_defconfig
> > DEFCONFIG_sh4 = rts7751r2dplus_defconfig
(...)
Thomas
next prev parent reply other threads:[~2026-01-06 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 22:14 Thomas Weißschuh
2026-01-05 7:44 ` Willy Tarreau
2026-01-05 8:19 ` Thomas Weißschuh
2026-01-05 8:31 ` Willy Tarreau
2026-01-06 11:40 ` Geert Uytterhoeven
2026-01-06 11:47 ` Thomas Weißschuh [this message]
2026-01-06 13:36 ` Geert Uytterhoeven
2026-01-06 18:32 ` Thomas Weißschuh
2026-01-06 19:34 ` Geert Uytterhoeven
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=18bb48f2-b5aa-42a6-bc09-4773e1907670@t-8ch.de \
--to=linux@weissschuh.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®