From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: andy.chiu@sifive.com, linux-riscv@lists.infradead.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] RISC-V: Remove unused "size" in ptrace
Date: Thu, 31 Aug 2023 17:31:51 +0100 [thread overview]
Message-ID: <20230831-pushup-race-b5820aa4bb7a@spud> (raw)
In-Reply-To: <20230830203754.24940-1-palmer@rivosinc.com>
[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]
On Wed, Aug 30, 2023 at 01:37:54PM -0700, Palmer Dabbelt wrote:
> Looks like this just got lost somewhere in the respins.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202308310306.tOrkoBmI-lkp@intel.com/
> Fixes: dbe46b094026 ("RISC-V: Add ptrace support for vectors")
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Huh, wonder how the patchwork automation missed that. Probably as good a
reminder as any to update the toolchains in use there.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-08-31 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 20:37 [PATCH] RISC-V: Remove unused "size" in ptrace Palmer Dabbelt
2023-08-31 16:31 ` Conor Dooley [this message]
2023-08-31 17:19 ` Nick Desaulniers
2023-08-31 17:19 ` Nick Desaulniers
2023-08-31 21:58 ` Palmer Dabbelt
2023-08-31 22:02 ` Palmer Dabbelt
2023-08-31 22:00 ` patchwork-bot+linux-riscv
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=20230831-pushup-race-b5820aa4bb7a@spud \
--to=conor@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--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 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.