Re: [PATCH] tools: add forwarding header for arch/riscv/include/asm/fence.h

From: "Björn Töpel" <bjorn@kernel.org>
To: Andreas Schwab <schwab@suse.de>, Alexandre Ghiti <alex@ghiti.fr>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: linux-riscv@lists.infradead.org,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Charlie Jenkins" <charlie@rivosinc.com>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Andrea Parri" <parri.andrea@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: add forwarding header for arch/riscv/include/asm/fence.h
Date: Tue, 12 Nov 2024 12:36:51 +0100	[thread overview]
Message-ID: <87h68cu1ik.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <mvmbjymxdsc.fsf@suse.de>

Andreas Schwab <schwab@suse.de> writes:

> On Nov 11 2024, Alexandre Ghiti wrote:
>
>> Indeed, Bjorn's patches did not make it into rc7...
>
> That needs to be fixed ASAP!

Ok, if we want to unbreak the tools builds, two series are required for
6.12.

[1] which addresses the asm/fence.h path issue
[2] which addresses the same issue, but for non-cross builds

[2] can be pulled to RISC-V fixes, but [1] reside in the bpf-next tree
(target 6.13). Details here: [3].

To reiterate what I asked Andrii, but for RISC-V fixes: Would it be
possible to pull these patches [2] into the RISC-V tree, having a
duplicate set in bpf-next? Or are we stuck with stable backporting, as
Andrii suggests?

Björn

[1] https://lore.kernel.org/linux-riscv/20240927131355.350918-1-bjorn@kernel.org/
[2] https://lore.kernel.org/linux-riscv/20241106193208.290067-1-bjorn@kernel.org/
[3] https://lore.kernel.org/linux-riscv/CAEf4BzZbq9OwSGi4pdb5_q8YkErfFiQFKYXg3g1rjpdejafx+Q@mail.gmail.com/

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv