From: Tom Tromey <tom@tromey.com>
To: Jim Wilson <jimw@sifive.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] fix ARI warnings for RISC-V port and fallout
Date: Fri, 11 Oct 2019 13:15:00 -0000 [thread overview]
Message-ID: <87h84f4e4q.fsf@tromey.com> (raw)
In-Reply-To: <CAFyWVaYZZ4PNygCCbXfKPDZMAvKgZYTn+yqzJkXRYbH3z_tVQg@mail.gmail.com> (Jim Wilson's message of "Thu, 10 Oct 2019 16:54:10 -0700")
>>>>> "Jim" == Jim Wilson <jimw@sifive.com> writes:
Jim> The first patch fixes the RISC-V ARI warnings reported in July. The
Jim> second patch fixes problems with the print-utils.h function comments I
Jim> noticed because I had to figure out what they did to write the first
Jim> patch.
Jim> This was tested with a riscv64-linux build and check, with no
Jim> regressions. I also tested gdb by hand to verify that the debugging
Jim> comment was still correct after the change as there is no testcase for
Jim> that.
I read these and they look fine to me. Thanks for doing this.
Tom
prev parent reply other threads:[~2019-10-11 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 23:54 Jim Wilson
2019-10-10 23:55 ` [PATCH 1/2] RISC-V: Fix two ARI warnings Jim Wilson
2019-10-10 23:55 ` [PATCH 2/2] Improve comments in print-utils.h Jim Wilson
2019-10-11 13:15 ` Tom Tromey [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=87h84f4e4q.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jimw@sifive.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