From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH 1/6] gdb/linux-nat: use get_ptrace_pid in two spots
Date: Mon, 05 Dec 2022 13:39:22 -0700 [thread overview]
Message-ID: <87pmcxk2kl.fsf@tromey.com> (raw)
In-Reply-To: <20221202200925.245955-1-simon.marchi@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Fri, 2 Dec 2022 15:09:20 -0500")
Simon> No behavior change expected.
I read through these & they all look good to me.
Tom
next prev parent reply other threads:[~2022-12-05 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 20:09 Simon Marchi
2022-12-02 20:09 ` [PATCH 2/6] gdb/linux-nat: bool-ify linux_nat_get_siginfo Simon Marchi
2022-12-02 20:09 ` [PATCH 3/6] gdb/linux-nat: don't memset siginfo on failure in linux_nat_get_siginfo Simon Marchi
2022-12-02 20:09 ` [PATCH 4/6] gdb/linux-nat: check ptrace return value " Simon Marchi
2022-12-02 20:09 ` [PATCH 5/6] gdb/linux-nat: use l linux_nat_get_siginfo in linux_xfer_siginfo Simon Marchi
2022-12-02 20:09 ` [PATCH 6/6] gdb/linux-nat: add ptid parameter to linux_xfer_siginfo Simon Marchi
2022-12-05 20:39 ` Tom Tromey [this message]
2022-12-05 21:39 ` [PATCH 1/6] gdb/linux-nat: use get_ptrace_pid in two spots Simon Marchi
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=87pmcxk2kl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).