Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/tdep] Don't call WaitForSingleObject with INFINITE arg
Date: Mon, 9 Jun 2025 18:52:21 +0100	[thread overview]
Message-ID: <9b923bac-ca60-430a-9e0a-17a16f93e6e9@palves.net> (raw)
In-Reply-To: <3111debd-c02c-4254-8ecf-0b0de2fea808@palves.net>

Hi again,

On 2025-06-06 16:27, Pedro Alves wrote:

> OK, I've sent that patch now:
> 
>   https://inbox.sourceware.org/gdb-patches/20250606152500.947489-1-pedro@palves.net/T/#u

I think I've now sent all the testsuite patches that don't depend on the non-stop series,
or rather, the "set scheduler-locking on" support that comes with it.

Some of the posted patches have already been merged, and others have not.

I've pushed a new 'users/palves/windows-non-stop-v2-plus' branch to sourceware.org that contains
the whole non-stop v2 series rebased on today's master, plus all the testsuite patches that I've posted
that aren't merged yet, and the others that I've not posted yet.  There are a few unposted GDB patches
in there too.

Pedro Alves

  reply	other threads:[~2025-06-09 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 15:03 Tom de Vries
2025-06-05 16:15 ` Pedro Alves
2025-06-05 16:25   ` Pedro Alves
2025-06-06  6:27     ` Tom de Vries
2025-06-06  7:12   ` Tom de Vries
2025-06-06 15:14     ` Pedro Alves
2025-06-06 15:27       ` Pedro Alves
2025-06-09 17:52         ` Pedro Alves [this message]
2025-06-10  7:13           ` Tom de Vries
2025-06-06 13:11   ` Pedro Alves
2025-06-10  7:13     ` Tom de Vries
2025-06-10  9:51       ` Pedro Alves

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=9b923bac-ca60-430a-9e0a-17a16f93e6e9@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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