From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
ajones@ventanamicro.com, conor.dooley@microchip.com,
panqinglin2020@iscas.ac.cn, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -fixes 0/2] NAPOT Fixes
Date: Thu, 29 Feb 2024 22:10:34 +0000 [thread overview]
Message-ID: <170924463458.14902.8377993668813531698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227205016.121901-1-alexghiti@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 27 Feb 2024 21:50:14 +0100 you wrote:
> This contains 2 fixes for NAPOT: patch 1 disables the use of NAPOT
> mapping for vmalloc/vmap and patch 2 implements pte_leaf_size() to
> report NAPOT size.
>
> Alexandre Ghiti (2):
> Revert "riscv: mm: support Svnapot in huge vmap"
> riscv: Fix pte_leaf_size() for NAPOT
>
> [...]
Here is the summary with links:
- [-fixes,1/2] Revert "riscv: mm: support Svnapot in huge vmap"
https://git.kernel.org/riscv/c/16ab4646c905
- [-fixes,2/2] riscv: Fix pte_leaf_size() for NAPOT
https://git.kernel.org/riscv/c/e0fe5ab4192c
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-02-29 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 20:50 [PATCH -fixes 0/2] NAPOT Fixes Alexandre Ghiti
2024-02-27 20:50 ` [PATCH -fixes 1/2] Revert "riscv: mm: support Svnapot in huge vmap" Alexandre Ghiti
2024-02-27 20:50 ` [PATCH -fixes 2/2] riscv: Fix pte_leaf_size() for NAPOT Alexandre Ghiti
2024-02-29 22:10 ` 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=170924463458.14902.8377993668813531698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=panqinglin2020@iscas.ac.cn \
--cc=paul.walmsley@sifive.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