From: patchwork-bot+linux-riscv@kernel.org
To: Yu-Chien Peter Lin <peterlin@andestech.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, david@redhat.com,
akpm@linux-foundation.org, alexghiti@rivosinc.com,
bjorn@rivosinc.com, linux-kernel@vger.kernel.org,
conor.dooley@microchip.com
Subject: Re: [PATCH v4 0/3] Improve PTDUMP and introduce new fields
Date: Mon, 06 Nov 2023 15:00:28 +0000 [thread overview]
Message-ID: <169928282898.16503.17999232797960429532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230921025022.3989723-1-peterlin@andestech.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 21 Sep 2023 10:50:19 +0800 you wrote:
> This patchset enhances PTDUMP by providing additional information
> from pagetable entries.
>
> The first patch fixes the RSW field, while the second and third
> patches introduce the PBMT and NAPOT fields, respectively, for
> RV64 systems.
>
> [...]
Here is the summary with links:
- [v4,1/3] riscv: Improve PTDUMP to show RSW with non-zero value
https://git.kernel.org/riscv/c/d5d2c264d33b
- [v4,2/3] riscv: Introduce PBMT field to PTDUMP
https://git.kernel.org/riscv/c/0713ff337173
- [v4,3/3] riscv: Introduce NAPOT field to PTDUMP
https://git.kernel.org/riscv/c/015c3c370472
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-11-06 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 2:50 Yu Chien Peter Lin
2023-09-21 2:50 ` [PATCH v4 1/3] riscv: Improve PTDUMP to show RSW with non-zero value Yu Chien Peter Lin
2023-09-21 2:50 ` [PATCH v4 2/3] riscv: Introduce PBMT field to PTDUMP Yu Chien Peter Lin
2023-09-21 2:50 ` [PATCH v4 3/3] riscv: Introduce NAPOT " Yu Chien Peter Lin
2023-11-06 15: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=169928282898.16503.17999232797960429532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=david@redhat.com \
--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 \
/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®