Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@wdc.com>
To: Palmer Dabbelt <palmerdabbelt@google.com>
Cc: Pedro Alves <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 21:21:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.21.1912052104540.30965@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <mhng-579837a9-e241-4060-be67-188eff3fcbfa@palmerdabbelt-glaptop>

Hi Palmer,

> >  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.

 Thanks for your input; these however are generic changes so I wouldn't 
expect you to chime in and I've been waiting for a general maintainer to 
pick them.  I guess Pedro, who already commented on an earlier version of 
one of them, has been too busy with other stuff recently.  No worries, 
I'll keep pinging.

  Maciej


  reply	other threads:[~2019-12-05 21:21 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 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-06 20:52 ` [PATCH v2 4/4] Unregister the inferior from the event loop if failed to resume Maciej W. Rozycki
2020-02-19 13:40   ` Luis Machado
2019-11-06 20:52 ` [PATCH v2 3/4] Remove breakpoint step-over information " Maciej W. Rozycki
2020-01-21  8:29   ` Simon Marchi
2020-02-19 13:30   ` Luis Machado
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
2019-12-05 21:21     ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.21.1912052104540.30965@redsun52.ssa.fujisawa.hgst.com \
    --to=macro@wdc.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimw@sifive.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