From: Carl Love <cel@linux.ibm.com>
To: Luis Machado <luis.machado@arm.com>,
Guinevere Larsen <blarsen@redhat.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@palves.net>, Tom Tromey <tom@tromey.com>,
Simon Marchi <simark@simark.ca>
Subject: Re: [ PATCH 0/3] Fix GDB reverse execution behavior
Date: Tue, 02 Jan 2024 14:52:06 -0800 [thread overview]
Message-ID: <2f99e6be965bbdd45ff067ed5f60619b2de20eea.camel@linux.ibm.com> (raw)
In-Reply-To: <7dbd2c8ff8c14ab6c487f5c88ce4476a7d03a905.camel@linux.ibm.com>
GDB maintainers:
On Thu, 2023-12-14 at 08:10 -0800, Carl Love wrote:
> Luis, GDB maintainers:
>
> On Mon, 2023-12-11 at 14:40 +0000, Luis Machado wrote:
>
> <snip>
>
> > Let's wait until this Friday to see if there is any other feedback
> > regarding this series.
> >
> > Otherwise, LGTM.
> >
> > Approved-By: Luis Machado <luis.machado@arm.com>
>
> I have not seen any additional comments or objections to committing
> the
> patch series per Luis's approval. My personal rule is to never
> commit
> anything and then go on vacation, just in case something goes
> wrong. I
> will be out of the office starting tomorrow Dec 15 until Jan 2.
> Assuming there are no additional feedback with the patches between
> now
> and Jan 2, I will commit the patches in January when I return.
>
> Thanks for the approval. Have a great holiday.
>
I have not seen any objections to committing the patches.
I rebased the patches on the latest mainline tree. I retested the
three patches on Power 10, Power 9, Power 8 and X86-64. No
regressions were found. The three patches have been committed to
mainline.
Carl
next prev parent reply other threads:[~2024-01-02 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f624c5566d6a8a1014ecc38900ca1ba0202989ef.camel@linux.ibm.com>
[not found] ` <890101c23dd5fa60fcbf9d4b299cb2a533c260b7.camel@linux.ibm.com>
[not found] ` <1e702d8f-e5b4-4719-b1e7-42210f350305@arm.com>
[not found] ` <a01f4e5f3fd399e3a9a971421265b34d08e32388.camel@linux.ibm.com>
[not found] ` <643afce1-ab9b-4e8b-bcbb-5738dc409a28@arm.com>
[not found] ` <9e17008084c34f953f5318933436ec703250120a.camel@linux.ibm.com>
[not found] ` <92a751d1-a4b9-4c21-821e-a1dc67207516@arm.com>
[not found] ` <ee4ed81911a3196327c2aea3fa9a77f910a5e798.camel@linux.ibm.com>
2023-11-22 23:33 ` Carl Love
2023-11-30 11:36 ` Guinevere Larsen
2023-11-30 15:39 ` Carl Love
2023-11-30 15:43 ` Luis Machado
2023-12-11 14:40 ` Luis Machado
2023-12-14 16:10 ` Carl Love
2024-01-02 22:52 ` Carl Love [this message]
2023-11-30 15:45 ` Guinevere Larsen
2023-11-22 23:33 ` [ PATCH 1/3] " Carl Love
2023-11-29 11:44 ` Luis Machado
2023-11-29 16:30 ` Carl Love
2023-11-29 16:38 ` Luis Machado
2023-11-22 23:33 ` [ PATCH 2/3] " Carl Love
2023-11-29 11:44 ` Luis Machado
2023-11-22 23:33 ` [PATCH 3/3] " Carl Love
2023-11-29 11:46 ` Luis Machado
2023-11-29 16:30 ` Carl Love
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=2f99e6be965bbdd45ff067ed5f60619b2de20eea.camel@linux.ibm.com \
--to=cel@linux.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
--cc=tom@tromey.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).