From: Peter Zijlstra <peterz@infradead.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH 0/2] x86: Avoid CONFIG_X86_X32_ABI=y with llvm-objcopy
Date: Mon, 14 Mar 2022 21:13:50 +0100 [thread overview]
Message-ID: <Yi+h/h6xcTQBdQBY@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220314194842.3452-1-nathan@kernel.org>
On Mon, Mar 14, 2022 at 12:48:40PM -0700, Nathan Chancellor wrote:
> This is based on -tip x86/core and I would like for both patches to go
> with the IBT changes so that there is no build breakage.
>
> Masahiro Yamada (1):
> x86: Remove toolchain check for X32 ABI capability
>
> Nathan Chancellor (1):
> x86/Kconfig: Do not allow CONFIG_X86_X32_ABI=y with llvm-objcopy
>
Mucho gracias, I was indeed seeing a lot of that. I was also in the
process of rebasing that tree, so I'll stick these on top.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: alsa-devel@alsa-project.org, llvm@lists.linux.dev,
Masahiro Yamada <masahiroy@kernel.org>,
x86@kernel.org, Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86: Avoid CONFIG_X86_X32_ABI=y with llvm-objcopy
Date: Mon, 14 Mar 2022 21:13:50 +0100 [thread overview]
Message-ID: <Yi+h/h6xcTQBdQBY@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220314194842.3452-1-nathan@kernel.org>
On Mon, Mar 14, 2022 at 12:48:40PM -0700, Nathan Chancellor wrote:
> This is based on -tip x86/core and I would like for both patches to go
> with the IBT changes so that there is no build breakage.
>
> Masahiro Yamada (1):
> x86: Remove toolchain check for X32 ABI capability
>
> Nathan Chancellor (1):
> x86/Kconfig: Do not allow CONFIG_X86_X32_ABI=y with llvm-objcopy
>
Mucho gracias, I was indeed seeing a lot of that. I was also in the
process of rebasing that tree, so I'll stick these on top.
next prev parent reply other threads:[~2022-03-14 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 19:48 [PATCH 0/2] x86: Avoid CONFIG_X86_X32_ABI=y with llvm-objcopy Nathan Chancellor
2022-03-14 19:48 ` Nathan Chancellor
2022-03-14 19:48 ` [PATCH 1/2] x86: Remove toolchain check for X32 ABI capability Nathan Chancellor
2022-03-14 19:48 ` Nathan Chancellor
2022-03-15 10:43 ` [tip: x86/core] " tip-bot2 for Masahiro Yamada
2022-03-14 19:48 ` [PATCH 2/2] x86/Kconfig: Do not allow CONFIG_X86_X32_ABI=y with llvm-objcopy Nathan Chancellor
2022-03-14 19:48 ` Nathan Chancellor
2022-03-15 10:43 ` [tip: x86/core] " tip-bot2 for Nathan Chancellor
2022-03-14 20:13 ` Peter Zijlstra [this message]
2022-03-14 20:13 ` [PATCH 0/2] x86: Avoid " Peter Zijlstra
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=Yi+h/h6xcTQBdQBY@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alsa-devel@alsa-project.org \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=x86@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.