From: Tom Tromey <tom@tromey.com>
To: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
Cc: Tom Tromey <tom@tromey.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>,
Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix AIX build break.
Date: Wed, 31 Jan 2024 17:37:42 -0700 [thread overview]
Message-ID: <87le85nhnt.fsf@tromey.com> (raw)
In-Reply-To: <CH2PR15MB3544BD28782FA7B1C6CFAD8ED67C2@CH2PR15MB3544.namprd15.prod.outlook.com> (Aditya Kamath1's message of "Wed, 31 Jan 2024 09:15:05 +0000")
>>>>> Aditya Kamath1 <Aditya.Kamath1@ibm.com> writes:
>> This looks basically reasonable, but rather than subject you to another
>> round of review, I just went ahead and made a few changes. Could you
>> try this out?
> This patch builds AIX GDB successfully. I am okay with this.
Thanks. I'm checking it in now.
Tom
next prev parent reply other threads:[~2024-02-01 0:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 18:28 Aditya Vidyadhar Kamath
2024-01-17 19:25 ` Tom Tromey
2024-01-19 11:58 ` Aditya Kamath1
2024-01-19 16:25 ` Tom Tromey
2024-01-20 15:03 ` Aditya Kamath1
2024-01-24 0:53 ` Aditya Kamath1
2024-01-25 14:45 ` Aditya Kamath1
2024-01-25 19:53 ` Tom Tromey
2024-01-26 8:37 ` Aditya Kamath1
2024-01-31 0:40 ` Tom Tromey
2024-01-31 9:15 ` Aditya Kamath1
2024-02-01 0:37 ` Tom Tromey [this message]
2024-02-01 3:03 ` Aditya Kamath1
2024-02-06 12:36 ` Ciaran Woodward
2024-02-06 14:49 ` Tom Tromey
2024-02-06 15:04 ` Ciaran Woodward
2024-02-06 15:54 ` Aditya Kamath1
-- strict thread matches above, loose matches on Subject: below --
2024-01-12 9:20 Aditya Kamath1
2024-01-12 9:50 ` Tom de Vries
2024-01-12 15:56 ` Tom Tromey
2024-01-16 9:42 ` Aditya Kamath1
2024-01-17 15:09 ` Tom Tromey
2023-08-11 8:49 Aditya Kamath1
2023-08-11 9:43 ` Ulrich Weigand
2023-08-11 9:53 ` Aditya Kamath1
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=87le85nhnt.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Aditya.Kamath1@ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).