All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, andy.chiu@sifive.com,
	bjorn@rivosinc.com, conor.dooley@microchip.com, heiko@sntech.de,
	vincent.chen@sifive.com, ben.dooks@codethink.co.uk,
	greentime.hu@sifive.com, ancientmodern4@gmail.com,
	jerry.shih@sifive.com, nick.knight@sifive.com,
	linux-kernel@vger.kernel.org, vineetg@rivosinc.com,
	charlie@rivosinc.com, vgupta@kernel.org
Subject: Re: [PATCH] riscv: Fix vector state restore in rt_sigreturn()
Date: Thu, 04 Apr 2024 19:40:29 +0000	[thread overview]
Message-ID: <171225962916.17194.17766920994807052898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240403072638.567446-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed,  3 Apr 2024 09:26:38 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> The RISC-V Vector specification states in "Appendix D: Calling
> Convention for Vector State" [1] that "Executing a system call causes
> all caller-saved vector registers (v0-v31, vl, vtype) and vstart to
> become unspecified.". In the RISC-V kernel this is called "discarding
> the vstate".
> 
> [...]

Here is the summary with links:
  - riscv: Fix vector state restore in rt_sigreturn()
    https://git.kernel.org/riscv/c/c27fa53b858b

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



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, andy.chiu@sifive.com,
	bjorn@rivosinc.com, conor.dooley@microchip.com, heiko@sntech.de,
	vincent.chen@sifive.com, ben.dooks@codethink.co.uk,
	greentime.hu@sifive.com, ancientmodern4@gmail.com,
	jerry.shih@sifive.com, nick.knight@sifive.com,
	linux-kernel@vger.kernel.org, vineetg@rivosinc.com,
	charlie@rivosinc.com, vgupta@kernel.org
Subject: Re: [PATCH] riscv: Fix vector state restore in rt_sigreturn()
Date: Thu, 04 Apr 2024 19:40:29 +0000	[thread overview]
Message-ID: <171225962916.17194.17766920994807052898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240403072638.567446-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed,  3 Apr 2024 09:26:38 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> The RISC-V Vector specification states in "Appendix D: Calling
> Convention for Vector State" [1] that "Executing a system call causes
> all caller-saved vector registers (v0-v31, vl, vtype) and vstart to
> become unspecified.". In the RISC-V kernel this is called "discarding
> the vstate".
> 
> [...]

Here is the summary with links:
  - riscv: Fix vector state restore in rt_sigreturn()
    https://git.kernel.org/riscv/c/c27fa53b858b

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-04-04 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  7:26 [PATCH] riscv: Fix vector state restore in rt_sigreturn() Björn Töpel
2024-04-03  7:26 ` Björn Töpel
2024-04-03 10:12 ` Andy Chiu
2024-04-03 10:12   ` Andy Chiu
2024-04-03 17:33 ` Vineet Gupta
2024-04-03 17:33   ` Vineet Gupta
2024-04-04 19:40 ` patchwork-bot+linux-riscv [this message]
2024-04-04 19:40   ` patchwork-bot+linux-riscv
2024-12-04  4:45 ` Yangyu Chen
2024-12-04  4:45   ` Yangyu Chen
2024-12-04 15:42 ` Sasha Levin
2024-12-04 22:12   ` Sasha Levin

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=171225962916.17194.17766920994807052898.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
    --cc=ancientmodern4@gmail.com \
    --cc=andy.chiu@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ben.dooks@codethink.co.uk \
    --cc=bjorn@rivosinc.com \
    --cc=charlie@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=greentime.hu@sifive.com \
    --cc=heiko@sntech.de \
    --cc=jerry.shih@sifive.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=nick.knight@sifive.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=vgupta@kernel.org \
    --cc=vincent.chen@sifive.com \
    --cc=vineetg@rivosinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.