From: patchwork-bot+linux-riscv@kernel.org
To: Dylan Jhong <dylan@andestech.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
guoren@kernel.org, sergey.matyukevich@syntacore.com,
aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com, x5710999x@gmail.com,
tim609@andestech.com, peterlin@andestech.com,
ycliang@andestech.com
Subject: Re: [PATCH v2] riscv: mm: Fix incorrect ASID argument when flushing TLB
Date: Thu, 23 Mar 2023 21:00:20 +0000 [thread overview]
Message-ID: <167960522086.10481.6194294455098619740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313034906.2401730-1-dylan@andestech.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 13 Mar 2023 11:49:06 +0800 you wrote:
> Currently, we pass the CONTEXTID instead of the ASID to the TLB flush
> function. We should only take the ASID field to prevent from touching
> the reserved bit field.
>
> Fixes: 3f1e782998cd ("riscv: add ASID-based tlbflushing methods")
> Signed-off-by: Dylan Jhong <dylan@andestech.com>
>
> [...]
Here is the summary with links:
- [v2] riscv: mm: Fix incorrect ASID argument when flushing TLB
https://git.kernel.org/riscv/c/9a801afd3eb9
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:[~2023-03-23 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 3:49 [PATCH v2] riscv: mm: Fix incorrect ASID argument when flushing TLB Dylan Jhong
2023-03-13 5:58 ` Sergey Matyukevich
2023-03-14 2:22 ` Zong Li
2023-03-14 7:27 ` Dylan Jhong
2023-03-21 2:42 ` Dylan Jhong
2023-03-22 5:45 ` Palmer Dabbelt
2023-03-23 20:47 ` Palmer Dabbelt
2023-03-23 21:00 ` 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=167960522086.10481.6194294455098619740.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=dylan@andestech.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterlin@andestech.com \
--cc=sergey.matyukevich@syntacore.com \
--cc=tim609@andestech.com \
--cc=x5710999x@gmail.com \
--cc=ycliang@andestech.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