mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>
Cc: Shuah Khan <shuah@kernel.org>, Zhangjin Wu <falcon@tinylab.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 3/6] selftests/nolibc: use XARCH for MIPS
Date: Sun, 5 Nov 2023 11:49:08 +0100	[thread overview]
Message-ID: <5f35c048-c0bc-4b16-a655-cea54c9f8cf9@t-8ch.de> (raw)
In-Reply-To: <ZUdvO9moDc7X5E54@1wt.eu>

On 2023-11-05 11:32:27+0100, Willy Tarreau wrote:
> On Sun, Nov 05, 2023 at 11:09:57AM +0100, Thomas Weißschuh wrote:
> > MIPS has many different configurations prepare the support of additional
> > ones by moving the build of MIPS to the generic XARCH infrastructure.
> > 
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
> >  tools/testing/selftests/nolibc/Makefile     | 12 +++++++-----
> >  tools/testing/selftests/nolibc/run-tests.sh |  2 +-
> >  2 files changed, 8 insertions(+), 6 deletions(-)
> > 
> > diff --git a/tools/testing/selftests/nolibc/Makefile b/tools/testing/selftests/nolibc/Makefile
> > index c5df1617cbc3..15c12f3c27ba 100644
> > --- a/tools/testing/selftests/nolibc/Makefile
> > +++ b/tools/testing/selftests/nolibc/Makefile
> > @@ -40,12 +40,14 @@ objtree ?= $(srctree)
> >  
> >  # configure default variants for target kernel supported architectures
> >  XARCH_powerpc    = ppc
> > +XARCH_mips       = mipso32le
> >  XARCH            = $(or $(XARCH_$(ARCH)),$(ARCH))
> >  
> >  # map from user input variants to their kernel supported architectures
> >  ARCH_ppc         = powerpc
> >  ARCH_ppc64       = powerpc
> >  ARCH_ppc64le     = powerpc
> > +ARCH_mipso32le   = mips
> 
> I *think* that what you called "mipso32le" above corresponds exactly to
> what is commonly called "mips32le" in toolchains or distros, because,
> unless I'm mistaken, "mips32" currently uses the O32 ABI. So that would
> sound more intuitive and natural I think.

Ack.

I did the same for mipso32be -> mips32be.

Thomas

  reply	other threads:[~2023-11-05 10:49 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 [this message]
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
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=5f35c048-c0bc-4b16-a655-cea54c9f8cf9@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=falcon@tinylab.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®