[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62e993a5-0bb4-40dc-6399-f60525300a6c@infradead.org>
Date: Thu, 6 Jul 2023 14:36:05 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Palmer Dabbelt <palmer@...belt.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, Conor Dooley <conor@...nel.org>
Subject: Re: linux-next: Tree for Jul 6 (arch/riscv/)
On 7/6/23 14:32, Palmer Dabbelt wrote:
> On Thu, 06 Jul 2023 14:27:53 PDT (-0700), rdunlap@...radead.org wrote:
>>
>>
>> On 7/5/23 18:57, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do *not* add any v6.6 related stuff to your linux-next included
>>> branches until after v6.5-rc1 has been released.
>>>
>>> Changes since 20230705:
>>>
>>
>> on riscv64:
>>
>> WARNING: modpost: vmlinux: section mismatch in reference: $xrv64i2p1_m2p0_a2p1_zicsr2p0_zifencei2p0_zihintpause2p0_zmmul1p0+0x14 (section: .text.unlikely.set_bit.constprop.0) -> numa_nodes_parsed (section: .init.data)
>>
>>
>> Full randconfig file is attached.
>
> Thanks, I'm giving it a look. Do you happen to also have your toolchain version easily availiable? The mapping symbols are new and we've seen some odd stuff happen, something is likely broken somewhere...
I'm using gcc-13.1.0 from https://mirrors.edge.kernel.org/pub/tools/crosstool/
--
~Randy
Powered by blists - more mailing lists