From: Pedro Alves <pedro@palves.net>
To: Lancelot Six <lancelot.six@amd.com>, gdb-patches@sourceware.org
Cc: lsix@lancelotsix.com
Subject: Re: [PATCH 1/2] gdb/testsuite/rocm: Add the hip_devices_support_debug_multi_process proc
Date: Fri, 28 Jul 2023 19:00:22 +0100 [thread overview]
Message-ID: <067644af-e984-2212-fe63-39a186f7a98b@palves.net> (raw)
In-Reply-To: <20230630145755.6500-2-lancelot.six@amd.com>
On 2023-06-30 15:57, Lancelot Six via Gdb-patches wrote:
> +
> +# Return true if all the devices supports debugging multiple processes
supports -> support
> +# using the GPU.
> +
Otherwise,
Approved-By: Pedro Alves <pedro@palves.net>
next prev parent reply other threads:[~2023-07-28 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:57 [PATCH 0/2] Fix debugging multi inferiors using the ROCm runtime Lancelot Six
2023-06-30 14:57 ` [PATCH 1/2] gdb/testsuite/rocm: Add the hip_devices_support_debug_multi_process proc Lancelot Six
2023-07-28 18:00 ` Pedro Alves [this message]
2023-06-30 14:57 ` [PATCH 2/2] gdb/amdgpu: Fix debugging multiple inferiors using the ROCm runtime Lancelot Six
2023-07-28 18:01 ` Pedro Alves
2023-07-28 18:04 ` Pedro Alves
2023-07-28 16:47 ` [PING] [PATCH 0/2] Fix debugging multi " Lancelot SIX
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=067644af-e984-2212-fe63-39a186f7a98b@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=lsix@lancelotsix.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).