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>
Subject: Re: linux-next: Tree for Jan 18 (arch/riscv/mm/init.c)
Date: Thu, 18 Jan 2024 09:47:10 -0800 [thread overview]
Message-ID: <344dca85-5c48-44e1-bc64-4fa7973edd12@infradead.org> (raw)
In-Reply-To: <20240118143152.3c34b117@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
On 1/17/24 19:31, Stephen Rothwell wrote:
> Hi all,
>
> News: the merge window has opened, so please do not add any material
> intended for v6.9 to your linux-next included branches until asfter
> v6.8-rc1 has been released.
>
> Changes since 20240117:
>
on riscv 32-bit:
../arch/riscv/mm/init.c: In function 'setup_vm':
../arch/riscv/mm/init.c:1063:34: error: 'PAGE_OFFSET_L3' undeclared (first use in this function); did you mean 'PAGE_OFFSET'?
1063 | kernel_map.page_offset = PAGE_OFFSET_L3;
| ^~~~~~~~~~~~~~
| PAGE_OFFSET
../arch/riscv/mm/init.c:1063:34: note: each undeclared identifier is reported only once for each function it appears in
PAGE_OFFSET_L3 is only defined for CONFIG_64BIT.
Full randconfig file is attached (fwiw).
--
#Randy
[-- Attachment #2: config-r5397.gz --]
[-- Type: application/gzip, Size: 22503 bytes --]
next prev parent reply other threads:[~2024-01-18 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 3:31 linux-next: Tree for Jan 18 Stephen Rothwell
2024-01-18 17:47 ` Randy Dunlap [this message]
2024-01-18 21:24 ` linux-next: Tree for Jan 18 (arch/riscv/mm/init.c) Alexandre Ghiti
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=344dca85-5c48-44e1-bc64-4fa7973edd12@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).