public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel•org
To: Alexandre Ghiti <alexghiti@rivosinc•com>
Cc: linux-riscv@lists•infradead.org, rdunlap@infradead•org,
	sfr@canb•auug.org.au, linux-next@vger•kernel.org,
	paul.walmsley@sifive•com, palmer@dabbelt•com,
	aou@eecs•berkeley.edu, haxel@fzi•de,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH] riscv: Fix build error on rv32 + XIP
Date: Sat, 20 Jan 2024 21:09:59 +0000	[thread overview]
Message-ID: <170578499912.24348.17976593950031551472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240118212120.2087803-1-alexghiti@rivosinc.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc•com>:

On Thu, 18 Jan 2024 22:21:20 +0100 you wrote:
> commit 66f1e6809397 ("riscv: Make XIP bootable again") restricted page
> offset to the sv39 page offset instead of the default sv57, which makes
> sense since probably the platforms that target XIP kernels do not
> support anything else than sv39 and we do not try to find out the
> largest address space supported on XIP kernels (ie set_satp_mode()).
> 
> But PAGE_OFFSET_L3 is not defined for rv32, so fix the build error by
> restoring the previous behaviour which picks CONFIG_PAGE_OFFSET for rv32.
> 
> [...]

Here is the summary with links:
  - riscv: Fix build error on rv32 + XIP
    https://git.kernel.org/riscv/c/66f962d8939f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-01-20 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 21:21 [PATCH] riscv: Fix build error on rv32 + XIP Alexandre Ghiti
2024-01-18 21:27 ` Randy Dunlap
2024-01-20 21:09 ` patchwork-bot+linux-riscv [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=170578499912.24348.17976593950031551472.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel$(echo .)org \
    --cc=alexghiti@rivosinc$(echo .)com \
    --cc=aou@eecs$(echo .)berkeley.edu \
    --cc=haxel@fzi$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-riscv@lists$(echo .)infradead.org \
    --cc=palmer@dabbelt$(echo .)com \
    --cc=paul.walmsley@sifive$(echo .)com \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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