public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, alexghiti@rivosinc.com,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/8] remove size limit on XIP kernel
Date: Sat, 14 Sep 2024 08:13:10 +0000	[thread overview]
Message-ID: <172630159029.2498524.2048412782900676166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1717789719.git.namcao@linutronix.de>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.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



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2024-09-14  8:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 20:22 [PATCH v2 0/8] remove size limit on XIP kernel Nam Cao
2024-06-07 20:22 ` [PATCH v2 1/8] riscv: cleanup XIP_FIXUP macro Nam Cao
2024-06-07 20:22 ` [PATCH v2 2/8] riscv: don't export va_kernel_pa_offset in vmcoreinfo for XIP kernel Nam Cao
2024-06-21 10:27   ` Alexandre Ghiti
2024-06-07 20:22 ` [PATCH v2 3/8] riscv: replace misleading va_kernel_pa_offset on " Nam Cao
2024-06-07 20:22 ` [PATCH v2 4/8] riscv: drop the use of XIP_OFFSET in XIP_FIXUP_OFFSET Nam Cao
2024-06-07 20:22 ` [PATCH v2 5/8] riscv: drop the use of XIP_OFFSET in XIP_FIXUP_FLASH_OFFSET Nam Cao
2024-06-07 20:22 ` [PATCH v2 6/8] riscv: drop the use of XIP_OFFSET in kernel_mapping_va_to_pa() Nam Cao
2024-06-07 20:22 ` [PATCH v2 7/8] riscv: drop the use of XIP_OFFSET in create_kernel_page_table() Nam Cao
2024-06-07 20:22 ` [PATCH v2 8/8] riscv: remove limit on the size of read-only section for XIP kernel Nam Cao
2024-09-14  8:13 ` 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=172630159029.2498524.2048412782900676166.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    /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