From: patchwork-bot+linux-riscv@kernel.org
To: Qinglin Pan <panqinglin2020@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
ajones@ventanamicro.com, alexghiti@rivosinc.com
Subject: Re: [PATCH RESEND v1] riscv: mm: call best_map_size many times during linear-mapping
Date: Fri, 09 Dec 2022 22:00:16 +0000 [thread overview]
Message-ID: <167062321606.20606.12182083440436811475.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221128023643.329091-1-panqinglin2020@iscas.ac.cn>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 28 Nov 2022 10:36:43 +0800 you wrote:
> From: Qinglin Pan <panqinglin2020@iscas.ac.cn>
>
> Modify the best_map_size function to give map_size many times instead
> of only once, so a memory region can be mapped by both PMD_SIZE and
> PAGE_SIZE.
>
> Signed-off-by: Qinglin Pan <panqinglin2020@iscas.ac.cn>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
> Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>
> Tested-by: Alexandre Ghiti <alexghiti@rivosinc.com>
>
> [...]
Here is the summary with links:
- [RESEND,v1] riscv: mm: call best_map_size many times during linear-mapping
https://git.kernel.org/riscv/c/6ff8ca3f93d3
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:[~2022-12-09 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 2:36 [PATCH RESEND v1] riscv: mm: call best_map_size many times during linear-mapping panqinglin2020
2022-12-09 21:54 ` Palmer Dabbelt
2022-12-09 22: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=167062321606.20606.12182083440436811475.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=panqinglin2020@iscas.ac.cn \
/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