Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Charlie Jenkins <charlie@rivosinc.com>,
	jiawei <jiawei@iscas.ac.cn>,
	 gdb-patches <gdb-patches@sourceware.org>,
	Binutils <binutils@sourceware.org>,
	 Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2] RISC-V: Fix disassembly of partial instructions
Date: Thu, 9 Jan 2025 10:14:08 +0800	[thread overview]
Message-ID: <CAPpQWtBppruU+owj1_qv77=BVyctrse89HCWDGYUqTVyxc5hcA@mail.gmail.com> (raw)
In-Reply-To: <87h66c2pzz.fsf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

Thanks Andrew, Jan, and Maciej.

I see the newest v4 patches, including test cases, so I committed them
after passed the regressions.

Thanks
Nelson

On Mon, Jan 6, 2025 at 6:31 PM Andrew Burgess <aburgess@redhat.com> wrote:

> Nelson Chu <nelson@rivosinc.com> writes:
>
> > Some minor GNU coding styles as follows.  Also cc Jan and Andrew, hope
> they
> > still have time in their busy schedules can help to see if there are some
> > side effects.
>
> I caught up on this thread today.  All the suggestions seem like good
> advice to me.  But I have no issues with the underlying fix, it seems
> like a good improvement to me.
>
> Acked-By: Andrew Burgess <aburgess@redhat.com>
>
> Thanks,
> Andrew
>
>

[-- Attachment #2: Type: text/html, Size: 1277 bytes --]

      reply	other threads:[~2025-01-09  2:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 22:23 Charlie Jenkins
2024-12-19 17:37 ` Nelson Chu
2024-12-19 18:37   ` Charlie Jenkins
2024-12-20 10:38   ` Jan Beulich
2024-12-20 19:27     ` Charlie Jenkins
2024-12-24  8:22       ` Jan Beulich
2025-01-02 19:14         ` Charlie Jenkins
2025-01-03  6:22           ` Maciej W. Rozycki
2025-01-03 19:23             ` Charlie Jenkins
2025-01-06  8:22             ` Jan Beulich
2025-01-06 10:30   ` Andrew Burgess
2025-01-09  2:14     ` Nelson Chu [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='CAPpQWtBppruU+owj1_qv77=BVyctrse89HCWDGYUqTVyxc5hcA@mail.gmail.com' \
    --to=nelson@rivosinc.com \
    --cc=aburgess@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=charlie@rivosinc.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=jiawei@iscas.ac.cn \
    /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