From: patchwork-bot+linux-riscv@kernel.org
To: Tong Tiangen <tongtiangen@huawei.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org, wangkefeng.wang@huawei.com,
guohanjun@huawei.com
Subject: Re: [PATCH -next 0/2]riscv/mm: two modifications on hugepage
Date: Fri, 02 Dec 2022 21:25:39 +0000 [thread overview]
Message-ID: <167001633987.19139.13919979874169762631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221024094725.3054311-1-tongtiangen@huawei.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 24 Oct 2022 09:47:23 +0000 you wrote:
> Tong Tiangen (2):
> riscv/mm: hugepage's PG_dcache_clean flag is only set in head page
> riscv/mm: add arch hook arch_clear_hugepage_flags
>
> arch/riscv/include/asm/cacheflush.h | 7 +++++++
> arch/riscv/include/asm/hugetlb.h | 6 ++++++
> arch/riscv/mm/cacheflush.c | 7 +++++++
> 3 files changed, 20 insertions(+)
Here is the summary with links:
- [-next,1/2] riscv/mm: hugepage's PG_dcache_clean flag is only set in head page
https://git.kernel.org/riscv/c/d33deda095d3
- [-next,2/2] riscv/mm: add arch hook arch_clear_hugepage_flags
https://git.kernel.org/riscv/c/d8bf77a1dc30
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:[~2022-12-02 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 9:47 [PATCH -next 0/2]riscv/mm: two modifications on hugepage Tong Tiangen
2022-10-24 9:47 ` [PATCH -next 1/2] riscv/mm: hugepage's PG_dcache_clean flag is only set in head page Tong Tiangen
2022-10-24 9:47 ` [PATCH -next 2/2] riscv/mm: add arch hook arch_clear_hugepage_flags Tong Tiangen
2022-12-02 21:03 ` [PATCH -next 0/2]riscv/mm: two modifications on hugepage Palmer Dabbelt
2022-12-02 21:25 ` 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=167001633987.19139.13919979874169762631.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tongtiangen@huawei.com \
--cc=wangkefeng.wang@huawei.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