From: patchwork-bot+linux-riscv@kernel.org
To: Frederik Haxel <haxel@fzi.de>
Cc: linux-riscv@lists.infradead.org, vitaly.wool@konsulko.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, greentime.hu@sifive.com,
andy.chiu@sifive.com, heiko@sntech.de,
conor.dooley@microchip.com, cleger@rivosinc.com,
samitolvanen@google.com, masahiroy@kernel.org, guoren@kernel.org,
namcaov@gmail.com, alexghiti@rivosinc.com,
akpm@linux-foundation.org, anup@brainfault.org, bhe@redhat.com,
chenjiahao16@huawei.com, bjorn@rivosinc.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix XIP boot and make XIP testable in QEMU
Date: Thu, 11 Jan 2024 14:50:37 +0000 [thread overview]
Message-ID: <170498463768.20080.204922306048177003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231212130116.848530-1-haxel@fzi.de>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 12 Dec 2023 14:01:11 +0100 you wrote:
> XIP boot seems to be broken for some time now. A likely reason why no one
> seems to have noticed this is that XIP is more difficult to test, as it is
> currently not easily testable with QEMU.
>
> These patches fix the XIP boot and allow an XIP build without BUILTIN_DTB,
> which in turn makes it easier to test an image with the QEMU virt machine.
>
> [...]
Here is the summary with links:
- [1/3] riscv: Make XIP bootable again
https://git.kernel.org/riscv/c/66f1e6809397
- [2/3] riscv: Fixed wrong register in XIP_FIXUP_FLASH_OFFSET macro
https://git.kernel.org/riscv/c/5daa37264102
- [3/3] riscv: Allow disabling of BUILTIN_DTB for XIP
https://git.kernel.org/riscv/c/6c4a2f6329f0
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
prev parent reply other threads:[~2024-01-11 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 13:01 [PATCH 0/3] Fix XIP boot and make XIP testable in QEMU Frederik Haxel
2023-12-12 13:01 ` [PATCH 1/3] riscv: Make XIP bootable again Frederik Haxel
2023-12-12 13:01 ` [PATCH 2/3] riscv: Fixed wrong register in XIP_FIXUP_FLASH_OFFSET macro Frederik Haxel
2023-12-12 13:01 ` [PATCH 3/3] riscv: Allow disabling of BUILTIN_DTB for XIP Frederik Haxel
2023-12-12 13:22 ` [PATCH 0/3] Fix XIP boot and make XIP testable in QEMU Conor Dooley
[not found] ` <CAM4kBBKBC=ZSQPzAq5MFQvd1g9=Up_oRAK5CV74oJHt=SbcPqg@mail.gmail.com>
2023-12-12 15:14 ` Conor Dooley
2023-12-13 16:08 ` Palmer Dabbelt
2024-01-11 14:50 ` 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=170498463768.20080.204922306048177003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=bhe@redhat.com \
--cc=bjorn@rivosinc.com \
--cc=chenjiahao16@huawei.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=haxel@fzi.de \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=namcaov@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samitolvanen@google.com \
--cc=vitaly.wool@konsulko.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