From: patchwork-bot+linux-riscv@kernel.org
To: Jesse Taube <jesse@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, ardb@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, nathan@kernel.org,
ndesaulniers@google.com, morbo@google.com,
justinstitt@google.com, alexghiti@rivosinc.com,
conor.dooley@microchip.com, masahiroy@kernel.org,
twd2.me@gmail.com, christophe.jaillet@wanadoo.fr,
samitolvanen@google.com, akpm@linux-foundation.org,
bhe@redhat.com, rppt@kernel.org, vishal.moola@gmail.com,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v4 0/4] RISC-V: Parse DT for Zkr to seed KASLR
Date: Wed, 14 Aug 2024 14:10:32 +0000 [thread overview]
Message-ID: <172364463227.2278280.4833968885789479932.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240709173937.510084-1-jesse@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 9 Jul 2024 13:39:33 -0400 you wrote:
> Add functions to pi/fdt_early.c to help parse the FDT to check if
> the isa string has the Zkr extension. Then use the Zkr extension to
> seed the KASLR base address.
>
> The first two patches fix the visibility of symbols.
>
> V1 -> V2:
> - Add RISC-V: pi: Force hidden visibility for all symbol references
> - Add RISC-V: pi: Add kernel/pi/pi.h
> - Rewrite archrandom_early.c to parse DT over checking the csr
> V2 -> V3:
> - Add RISC-V: lib: Add pi aliases for string functions
> - Rewrite isa_string_contains in third patch
>
> [...]
Here is the summary with links:
- [v4,1/4] RISC-V: pi: Force hidden visibility for all symbol references
https://git.kernel.org/riscv/c/14c3ec67236b
- [v4,2/4] RISC-V: lib: Add pi aliases for string functions
https://git.kernel.org/riscv/c/d57e19fcbf3f
- [v4,3/4] RISC-V: pi: Add kernel/pi/pi.h
https://git.kernel.org/riscv/c/b3311827155a
- [v4,4/4] RISC-V: Use Zkr to seed KASLR base address
https://git.kernel.org/riscv/c/945302df3de1
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-08-14 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 17:39 [PATCH v4 0/4] RISC-V: Parse DT for Zkr to seed KASLR Jesse Taube
2024-07-09 17:39 ` [PATCH v4 1/4] RISC-V: pi: Force hidden visibility for all symbol references Jesse Taube
2024-07-09 17:39 ` [PATCH v4 2/4] RISC-V: lib: Add pi aliases for string functions Jesse Taube
2024-07-09 17:39 ` [PATCH v4 3/4] RISC-V: pi: Add kernel/pi/pi.h Jesse Taube
2024-07-09 17:39 ` [PATCH v4 4/4] RISC-V: Use Zkr to seed KASLR base address Jesse Taube
2024-07-10 14:23 ` Conor Dooley
2024-08-14 14: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=172364463227.2278280.4833968885789479932.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=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor.dooley@microchip.com \
--cc=jesse@rivosinc.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=twd2.me@gmail.com \
--cc=vishal.moola@gmail.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