From: "yang.zhang" <gaoshanliukou@163.com>
To: patchwork-bot+linux-riscv@kernel.org
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,
yang.zhang@hexintek.com
Subject: Re:Re: [PATCH V3] riscv: set trap vector earlier
Date: Mon, 15 Jul 2024 13:42:16 +0800 (CST) [thread overview]
Message-ID: <4d0ea144.51f5.190b4e9c0f6.Coremail.gaoshanliukou@163.com> (raw)
In-Reply-To: <172098903367.7439.15717595350937923936.git-patchwork-notify@kernel.org>
hi:
Yeah, thanks.
At 2024-07-15 04:30:33, patchwork-bot+linux-riscv@kernel.org wrote:
>Hello:
>
>This patch was applied to riscv/linux.git (for-next)
>by Palmer Dabbelt <palmer@rivosinc.com>:
>
>On Wed, 8 May 2024 10:24:45 +0800 you wrote:
>> From: "yang.zhang" <yang.zhang@hexintek.com>
>>
>> The exception vector of the booting hart is not set before enabling
>> the mmu and then still points to the value of the previous firmware,
>> typically _start. That makes it hard to debug setup_vm() when bad
>> things happen. So fix that by setting the exception vector earlier.
>>
>> [...]
>
>Here is the summary with links:
> - [V3] riscv: set trap vector earlier
> https://git.kernel.org/riscv/c/6ad8735994b8
>
>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:[~2024-07-15 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 2:24 yang.zhang
2024-07-14 20:30 ` patchwork-bot+linux-riscv
2024-07-15 5:42 ` yang.zhang [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=4d0ea144.51f5.190b4e9c0f6.Coremail.gaoshanliukou@163.com \
--to=gaoshanliukou@163.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=patchwork-bot+linux-riscv@kernel.org \
--cc=paul.walmsley@sifive.com \
--cc=yang.zhang@hexintek.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
all inboxes | Powered by JetHome®