From: Will Deacon <will@kernel.org>
To: xur@google.com
Cc: Yabin Cui <yabinc@google.com>, Han Shen <shenhan@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Kees Cook <kees@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Linus Walleij <linusw@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Miguel Ojeda <ojeda@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Lukas Bulwahn <lukas.bulwahn@redhat.com>,
linux-kernel@vger.kernel.org, Juergen Gross <jgross@suse.com>,
Helge Deller <deller@gmx.de>, Ryan Roberts <ryan.roberts@arm.com>,
Marc Zyngier <maz@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Vincent Donnefort <vdonnefort@google.com>,
Alice Ryhl <aliceryhl@google.com>,
x86@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] kconfig: Remove the architecture specific config for AutoFDO and Propeller
Date: Fri, 29 May 2026 17:32:01 +0100 [thread overview]
Message-ID: <ahm_gd40d4rvD6L5@willie-the-truck> (raw)
In-Reply-To: <20260527214510.3907973-1-xur@google.com>
On Wed, May 27, 2026 at 02:45:06PM -0700, xur@google.com wrote:
> From: Rong Xu <xur@google.com>
>
> Resend this patch:
>
> ChangeLog:
> V3: (1) updated the base;
> (2) changed vmlinux.lds.S for arm64 to avoid the warnings
> from .llvm_bb_addr_map.
>
> Rong Xu (2):
> kconfig: Remove the architecture specific config for AutoFDO
> kconfig: Remove the architecture specific config for Propeller
>
> arch/Kconfig | 8 --------
> arch/arm64/kernel/vmlinux.lds.S | 3 +++
> arch/x86/Kconfig | 2 --
> 3 files changed, 3 insertions(+), 10 deletions(-)
For the series:
Acked-by: Will Deacon <will@kernel.org>
Will
prev parent reply other threads:[~2026-05-29 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 21:45 [PATCH v3 0/2] kconfig: Remove the architecture specific config for AutoFDO and Propeller xur
2026-05-27 21:45 ` [PATCH v3 1/2] kconfig: Remove the architecture specific config for AutoFDO xur
2026-05-30 0:47 ` Nathan Chancellor
2026-06-01 16:52 ` Rong Xu
2026-06-01 19:24 ` Nathan Chancellor
2026-05-27 21:45 ` [PATCH v3 2/2] kconfig: Remove the architecture specific config for Propeller xur
2026-05-30 0:47 ` Nathan Chancellor
2026-06-01 18:18 ` Rong Xu
2026-06-02 9:43 ` Will Deacon
2026-06-02 17:52 ` Rong Xu
2026-06-03 1:53 ` Nathan Chancellor
2026-06-03 22:15 ` Rong Xu
2026-06-04 14:39 ` Will Deacon
2026-05-29 16:32 ` Will Deacon [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=ahm_gd40d4rvD6L5@willie-the-truck \
--to=will@kernel.org \
--cc=aliceryhl@google.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=deller@gmx.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kees@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=shenhan@google.com \
--cc=tglx@linutronix.de \
--cc=vdonnefort@google.com \
--cc=x86@kernel.org \
--cc=xur@google.com \
--cc=yabinc@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