public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, andy.chiu@sifive.com
Subject: Re: [PATCH] RISC-V: Remove ptrace support for vectors
Date: Wed, 23 Aug 2023 19:40:23 +0000	[thread overview]
Message-ID: <169281962368.18988.16256998915618280339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230810214810.21905-1-palmer@rivosinc.com>

Hello:

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

On Thu, 10 Aug 2023 14:48:10 -0700 you wrote:
> We've found two bugs here: NT_RISCV_VECTOR steps on NT_RISCV_CSR (which
> is only for embedded), and we don't have vlenb in the core dumps.  Given
> that we've have a pair of bugs croup up as part of the GDB review we've
> probably got other issues, so let's just cut this for 6.5 and get it
> right.
> 
> Fixes: 0c59922c769a ("riscv: Add ptrace vector support")
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> 
> [...]

Here is the summary with links:
  - RISC-V: Remove ptrace support for vectors
    https://git.kernel.org/riscv/c/e3f9324b231a

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

      parent reply	other threads:[~2023-08-23 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 21:48 [PATCH] RISC-V: Remove ptrace support for vectors Palmer Dabbelt
2023-08-12 17:12 ` Maciej W. Rozycki
2023-08-23 19:40 ` 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=169281962368.18988.16256998915618280339.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=andy.chiu@sifive.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox