From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor@kernel.org>
Subject: Re: linux-next: Tree for Jul 6 (arch/riscv/)
Date: Thu, 6 Jul 2023 14:27:53 -0700 [thread overview]
Message-ID: <9d9e2902-5489-4bf0-d9cb-556c8e5d71c2@infradead.org> (raw)
In-Reply-To: <20230706115739.731867f1@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
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.
--
~Randy
[-- Attachment #2: config-r2635.gz --]
[-- Type: application/gzip, Size: 34413 bytes --]
next prev parent reply other threads:[~2023-07-06 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 1:57 linux-next: Tree for Jul 6 Stephen Rothwell
2023-07-06 21:07 ` linux-next: Tree for Jul 6 [drivers/vdpa/pds/pds_vdpa.ko] Randy Dunlap
2023-07-06 22:26 ` Shannon Nelson
2023-07-06 21:27 ` Randy Dunlap [this message]
2023-07-06 21:32 ` linux-next: Tree for Jul 6 (arch/riscv/) Palmer Dabbelt
2023-07-06 21:36 ` Randy Dunlap
2023-07-06 21:46 ` Palmer Dabbelt
2023-07-06 23:40 ` Randy Dunlap
2023-07-07 5:47 ` Palmer Dabbelt
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=9d9e2902-5489-4bf0-d9cb-556c8e5d71c2@infradead.org \
--to=rdunlap@infradead.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®