From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 0/8] MIPS: Aggregate build fixes
Date: Fri, 23 Feb 2024 10:18:00 +0100 [thread overview]
Message-ID: <ZdhiyFzR3sC4nc+p@alpha.franken.de> (raw)
In-Reply-To: <20240202-llvm-msym32-v1-0-52f0631057d6@flygoat.com>
On Fri, Feb 02, 2024 at 06:21:39PM +0000, Jiaxun Yang wrote:
> Hi all,
>
> This series is a collection of build fixes that have been lying
> at my local trees for a while, some of them are for Clang built
> linux and others are for some wiredo configurations.
>
> Please review.
>
> Thanks
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> Jiaxun Yang (8):
> MIPS: Probe toolchain support of -msym32
> MIPS: Remove cc-option checks for -march=octeon
> MIPS: Fallback CPU -march flag to ISA level if unsupported
> MIPS: BMIPS: Drop unnecessary assembler flag
> MIPS: Loongson64: test for -march=loongson3a cflag
> MIPS: Limit MIPS_MT_SMP support by ISA reversion
> MIPS: Implement microMIPS MT ASE helpers
> MIPS: mipsregs: Set proper ISA level for virt extensions
>
> arch/mips/Kconfig | 3 +-
> arch/mips/Makefile | 46 ++++---
> arch/mips/include/asm/asmmacro.h | 22 ++--
> arch/mips/include/asm/mipsmtregs.h | 256 ++++++++++++++++++++++---------------
> arch/mips/include/asm/mipsregs.h | 22 +++-
> arch/mips/kernel/vpe-mt.c | 4 +-
> 6 files changed, 211 insertions(+), 142 deletions(-)
> ---
> base-commit: 076d56d74f17e625b3d63cf4743b3d7d02180379
> change-id: 20240202-llvm-msym32-6392d410f650
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2024-02-23 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 18:21 [PATCH 0/8] MIPS: Aggregate build fixes Jiaxun Yang
2024-02-02 18:21 ` [PATCH 1/8] MIPS: Probe toolchain support of -msym32 Jiaxun Yang
2024-02-02 18:21 ` [PATCH 2/8] MIPS: Remove cc-option checks for -march=octeon Jiaxun Yang
2024-02-02 18:21 ` [PATCH 3/8] MIPS: Fallback CPU -march flag to ISA level if unsupported Jiaxun Yang
2024-02-02 18:21 ` [PATCH 4/8] MIPS: BMIPS: Drop unnecessary assembler flag Jiaxun Yang
2024-02-02 18:21 ` [PATCH 5/8] MIPS: Loongson64: test for -march=loongson3a cflag Jiaxun Yang
2024-02-02 18:21 ` [PATCH 6/8] MIPS: Limit MIPS_MT_SMP support by ISA reversion Jiaxun Yang
2024-05-14 21:38 ` Maciej W. Rozycki
2024-05-14 23:39 ` Jiaxun Yang
2024-05-15 13:43 ` Maciej W. Rozycki
2024-05-15 21:26 ` Jiaxun Yang
2024-05-16 22:44 ` Maciej W. Rozycki
2024-02-02 18:21 ` [PATCH 7/8] MIPS: Implement microMIPS MT ASE helpers Jiaxun Yang
2024-02-02 18:21 ` [PATCH 8/8] MIPS: mipsregs: Set proper ISA level for virt extensions Jiaxun Yang
2024-02-20 18:26 ` [PATCH 0/8] MIPS: Aggregate build fixes Jiaxun Yang
2024-02-23 9:18 ` Thomas Bogendoerfer [this message]
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=ZdhiyFzR3sC4nc+p@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jiaxun.yang@flygoat.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox