public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	leobras@redhat.com, aou@eecs.berkeley.edu, xiao.w.wang@intel.com,
	paul.walmsley@sifive.com, charlie@rivosinc.com,
	linux-kernel@vger.kernel.org, conor@kernel.org,
	conor.dooley@microchip.com, evan@rivosinc.com, guoren@kernel.org,
	andy.chiu@sifive.com, greentime.hu@sifive.com,
	cleger@rivosinc.com, tglx@linutronix.de, ajones@ventanamicro.com,
	ke.zhao@shingroup.cn, debug@rivosinc.com
Subject: Re: [PATCH v4 0/3] riscv: Per-thread envcfg CSR support
Date: Sun, 06 Oct 2024 13:29:18 +0000	[thread overview]
Message-ID: <172822135876.3395169.3761438771827436861.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240814081126.956287-1-samuel.holland@sifive.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 14 Aug 2024 01:10:53 -0700 you wrote:
> This series (or equivalent) is a prerequisite for both user-mode pointer
> masking and CFI support, as both of those are per-thread features and
> are controlled by fields in the envcfg CSR. These patches are based on
> v1 of the pointer masking series[1], with significant input from both
> Deepak and Andrew.
> 
> [1]: https://lore.kernel.org/linux-riscv/20240319215915.832127-6-samuel.holland@sifive.com/
> 
> [...]

Here is the summary with links:
  - [v4,1/3] riscv: Enable cbo.zero only when all harts support Zicboz
    https://git.kernel.org/riscv/c/1b57747e978f
  - [v4,2/3] riscv: Add support for per-thread envcfg CSR values
    https://git.kernel.org/riscv/c/5fc7355f0137
  - [v4,3/3] riscv: Call riscv_user_isa_enable() only on the boot hart
    https://git.kernel.org/riscv/c/368546ebe7e7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-10-06 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14  8:10 [PATCH v4 0/3] riscv: Per-thread envcfg CSR support Samuel Holland
2024-08-14  8:10 ` [PATCH v4 1/3] riscv: Enable cbo.zero only when all harts support Zicboz Samuel Holland
2024-09-12 23:01   ` Charlie Jenkins
2024-08-14  8:10 ` [PATCH v4 2/3] riscv: Add support for per-thread envcfg CSR values Samuel Holland
2024-09-12 23:01   ` Charlie Jenkins
2024-08-14  8:10 ` [PATCH v4 3/3] riscv: Call riscv_user_isa_enable() only on the boot hart Samuel Holland
2024-09-12 22:59   ` Charlie Jenkins
2024-10-06 13:29 ` 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=172822135876.3395169.3761438771827436861.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=andy.chiu@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=debug@rivosinc.com \
    --cc=evan@rivosinc.com \
    --cc=greentime.hu@sifive.com \
    --cc=guoren@kernel.org \
    --cc=ke.zhao@shingroup.cn \
    --cc=leobras@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@linutronix.de \
    --cc=xiao.w.wang@intel.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