From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, alex@ghiti.fr, songshuaishuai@tinylab.org,
cyrevolt@gmail.com, bjorn@rivosinc.com, mick@ics.forth.gr,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] riscv: kexec_file: Support loading Image binary file
Date: Mon, 02 Jun 2025 22:12:40 +0000 [thread overview]
Message-ID: <174890236014.925497.1303542607611345716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250409193004.643839-1-bjorn@kernel.org>
Hello:
This series was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Wed, 9 Apr 2025 21:29:57 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> Hi!
>
> For over a year ago, Daniel and I was testing the V2 of Song's series.
> I also promised to take the V2, that had been sitting on the lists for
> too long, to rebase it on a new kernel, and re-test it.
>
> [...]
Here is the summary with links:
- [v3,1/2] riscv: kexec_file: Split the loading of kernel and others
https://git.kernel.org/riscv/c/4abec7d96c18
- [v3,2/2] riscv: kexec_file: Support loading Image binary file
https://git.kernel.org/riscv/c/1d57a3df656f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-02 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 19:29 Björn Töpel
2025-04-09 19:29 ` [PATCH v3 1/2] riscv: kexec_file: Split the loading of kernel and others Björn Töpel
2025-04-09 19:29 ` [PATCH v3 2/2] riscv: kexec_file: Support loading Image binary file Björn Töpel
2025-04-10 1:44 ` [External] " yunhui cui
2025-04-10 6:40 ` Björn Töpel
2025-04-16 13:58 ` kernel test robot
2025-06-02 22:12 ` 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=174890236014.925497.1303542607611345716.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alex@ghiti.fr \
--cc=bjorn@rivosinc.com \
--cc=cyrevolt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=songshuaishuai@tinylab.org \
/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
all inboxes | Powered by JetHome®