[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172630159029.2498524.2048412782900676166.git-patchwork-notify@kernel.org>
Date: Sat, 14 Sep 2024 08:13:10 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Nam Cao <namcao@...utronix.de>
Cc: linux-riscv@...ts.infradead.org, alexghiti@...osinc.com,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/8] remove size limit on XIP kernel
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@...osinc.com>:
On Fri, 7 Jun 2024 22:22:05 +0200 you wrote:
> Hi,
>
> For XIP kernel, the writable data section is always at offset specified in
> XIP_OFFSET, which is hard-coded to 32MB.
>
> Unfortunately, this means the read-only section (placed before the
> writable section) is restricted in size. This causes build failure if the
> kernel gets too large.
>
> [...]
Here is the summary with links:
- [v2,1/8] riscv: cleanup XIP_FIXUP macro
https://git.kernel.org/riscv/c/aa3457f22f00
- [v2,2/8] riscv: don't export va_kernel_pa_offset in vmcoreinfo for XIP kernel
https://git.kernel.org/riscv/c/f2df5b4fdd74
- [v2,3/8] riscv: replace misleading va_kernel_pa_offset on XIP kernel
https://git.kernel.org/riscv/c/5cf089672119
- [v2,4/8] riscv: drop the use of XIP_OFFSET in XIP_FIXUP_OFFSET
https://git.kernel.org/riscv/c/e4eac34feda4
- [v2,5/8] riscv: drop the use of XIP_OFFSET in XIP_FIXUP_FLASH_OFFSET
https://git.kernel.org/riscv/c/23311f57ee13
- [v2,6/8] riscv: drop the use of XIP_OFFSET in kernel_mapping_va_to_pa()
https://git.kernel.org/riscv/c/75fdf791dff0
- [v2,7/8] riscv: drop the use of XIP_OFFSET in create_kernel_page_table()
https://git.kernel.org/riscv/c/a7cfb999433a
- [v2,8/8] riscv: remove limit on the size of read-only section for XIP kernel
https://git.kernel.org/riscv/c/b635a84bde6f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists