From: "Palmer Dabbelt via gdb-patches" <gdb-patches@sourceware.org>
To: macro@wdc.com
Cc: palves@redhat.com, gdb-patches@sourceware.org,
Jim Wilson <jimw@sifive.com>
Subject: Re: [PING^3][PATCH v2 0/4] GDB fixes for the remote end having gone astray
Date: Thu, 05 Dec 2019 20:59:00 -0000 [thread overview]
Message-ID: <mhng-579837a9-e241-4060-be67-188eff3fcbfa@palmerdabbelt-glaptop> (raw)
In-Reply-To: <alpine.LFD.2.21.1912021445290.13542@redsun52.ssa.fujisawa.hgst.com>
On Mon, 02 Dec 2019 06:50:11 PST (-0800), macro@wdc.com wrote:
> On Wed, 6 Nov 2019, Maciej W. Rozycki wrote:
>
>> As issues from software stepping having gone astray seem to have started
>> piling up, and with your suggested modifications there is now a dependency
>> between the changes, I have decided to make this patch submission a small
>> series with 1/4 and 3/4 corresponding to original individual submissions
>> and 2/4 and 4/4 being entrely new fixes.
>
> Ping for:
>
> <https://sourceware.org/ml/gdb-patches/2019-11/msg00191.html>
> <https://sourceware.org/ml/gdb-patches/2019-11/msg00192.html>
> <https://sourceware.org/ml/gdb-patches/2019-11/msg00193.html>
> <https://sourceware.org/ml/gdb-patches/2019-11/msg00194.html>
Sorry, but these are way over my head. I've had the patches sitting in my
inbox for a while now in the hope that I could review them, but I'm afraid I'm
going to have to drop them -- I certainly have no opposition to the patches, I
just don't know enough to review them.
next prev parent reply other threads:[~2019-12-05 20:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 20:51 [PATCH " Maciej W. Rozycki
2019-11-06 20:51 ` [PATCH v2 1/4] Remove stale breakpoint step-over information Maciej W. Rozycki
2020-01-21 5:41 ` Simon Marchi
2020-02-19 11:26 ` Luis Machado
2019-11-06 20:52 ` [PATCH v2 3/4] Remove breakpoint step-over information if failed to resume Maciej W. Rozycki
2020-01-21 8:29 ` Simon Marchi
2020-02-19 13:30 ` Luis Machado
2019-11-06 20:52 ` [PATCH v2 4/4] Unregister the inferior from the event loop " Maciej W. Rozycki
2020-02-19 13:40 ` Luis Machado
2019-11-06 20:52 ` [PATCH v2 2/4] Unregister the last inferior from the event loop Maciej W. Rozycki
2020-01-21 5:47 ` Simon Marchi
2020-01-21 11:21 ` Maciej W. Rozycki
2020-01-21 17:34 ` Simon Marchi
2020-01-22 17:35 ` Maciej W. Rozycki
2020-01-23 1:19 ` Maciej W. Rozycki
2020-01-23 5:39 ` Maciej W. Rozycki
2020-01-23 16:59 ` Simon Marchi
2019-11-18 12:38 ` [PING][PATCH v2 0/4] GDB fixes for the remote end having gone astray Maciej W. Rozycki
2019-11-26 15:49 ` [PING^2][PATCH " Maciej W. Rozycki
2019-12-02 14:50 ` [PING^3][PATCH " Maciej W. Rozycki
2019-12-05 20:59 ` Palmer Dabbelt via gdb-patches [this message]
2019-12-05 21:21 ` Maciej W. Rozycki
2019-12-09 21:29 ` [PING^4][PATCH " Maciej W. Rozycki
2019-12-17 0:06 ` [PING^5][PATCH " Maciej W. Rozycki
2020-01-06 15:40 ` [PING^6][PATCH " Maciej W. Rozycki
2020-01-13 20:46 ` [PING^7][PATCH " Maciej W. Rozycki
2020-01-21 4:21 ` [PING^8][PATCH " Maciej W. Rozycki
2020-02-10 9:01 ` [PING^10][PATCH " Maciej W. Rozycki
2020-02-17 14:07 ` [PATCH " Maciej W. Rozycki
2020-02-18 10:38 ` Luis Machado
2020-02-19 21:11 ` Tom Tromey
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=mhng-579837a9-e241-4060-be67-188eff3fcbfa@palmerdabbelt-glaptop \
--to=gdb-patches@sourceware.org \
--cc=jimw@sifive.com \
--cc=macro@wdc.com \
--cc=palmerdabbelt@google.com \
--cc=palves@redhat.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