From: Tom Tromey <tromey@adacore.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Fix an Ada sign-extension problem
Date: Thu, 23 Sep 2021 09:30:50 -0600 [thread overview]
Message-ID: <87h7eb5mxh.fsf@tromey.com> (raw)
In-Reply-To: <20210923105309.GA1900093@embecosm.com> (Andrew Burgess's message of "Thu, 23 Sep 2021 11:53:09 +0100")
Andrew> I looked through the series, all looks good with my one suggestion on
Andrew> patch #2.
Thanks. I'm checking this in with the various updates.
Tom
prev parent reply other threads:[~2021-09-23 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 17:10 Tom Tromey
2021-09-22 17:10 ` [PATCH 1/3] Remove defaulted 'tid' parameter to ptid_t constructor Tom Tromey
2021-09-22 17:22 ` John Baldwin
2021-09-22 17:10 ` [PATCH 2/3] Change ptid_t::tid to ULONGEST Tom Tromey
2021-09-22 17:24 ` John Baldwin
2021-09-22 20:44 ` Tom Tromey
2021-09-23 10:31 ` Andrew Burgess
2021-09-23 14:10 ` Tom Tromey
2021-09-22 17:10 ` [PATCH 3/3] Change get_ada_task_ptid parameter type Tom Tromey
2021-09-23 10:53 ` [PATCH 0/3] Fix an Ada sign-extension problem Andrew Burgess
2021-09-23 15:30 ` 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=87h7eb5mxh.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).