Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Timur Golubovich <timurgol007@gmail.com>,
	Andrew Burgess <aburgess@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [PING][PATCH v2] gdb/record: Support fense.tso, zicond, bitmanip,  sinval and zihintntl in riscv
Date: Mon, 27 Oct 2025 14:23:17 -0300	[thread overview]
Message-ID: <f30cfec2-9620-4019-b220-4326fc852f19@redhat.com> (raw)
In-Reply-To: <CADR_JzDGt1HrxO+4_K2qvcxcOLhFA1FDU6ykfbhY9ue_4NOy1w@mail.gmail.com>

On 10/27/25 1:17 PM, Timur Golubovich wrote:
> Hi! Polite ping:)
>
> 4 weeks have passed and there aren't any significant changes in this patch
> so I'm thinking of merging it this week if no one minds.

You can only decide to merge it if you would have the authority to 
approve patches in this area. In other words, if you were an area 
maintainer of the relevant area, or if you were a global maintainer. 
Unfortunately, you'll have to continue pinging until a global 
maintainer, or risc-v maintainer, approves this.

-- 
Cheers,
Guinevere Larsen
It/she

>
> On Fri Sep 26 19:30:51 2025, timurgol007 wrote:
>> gdb/record: Support fense.tso, zicond, bitmanip, sinval and zihintntl in RISC-V
>>
>> Added record-full support for these extensions. As some opcodes were
>> missed in riscv-opc.h, added them there using riscv-opcodes repo.
>>
>> gdb/riscv-tdep.c           | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---
>> include/opcode/riscv-opc.h | 43 +++++++++++++++++++++++++++++++++
>> 2 files changed, 123 insertions(+), 3 deletions(-)
>>


  reply	other threads:[~2025-10-27 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 16:17 Timur Golubovich
2025-10-27 17:23 ` Guinevere Larsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-20 11:39 timurgol007
2025-10-27 15:42 ` timurgol007
2025-10-31 17:37 ` Guinevere Larsen
2025-10-31 17:54   ` Tom Tromey

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=f30cfec2-9620-4019-b220-4326fc852f19@redhat.com \
    --to=guinevere@redhat.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=timurgol007@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