public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>,
	Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 1/2] gdbsupport, gdb: add read_text_file_to_string, use it in linux_common_core_of_thread
Date: Tue, 8 Nov 2022 16:52:53 -0500	[thread overview]
Message-ID: <33e56032-0f42-84c5-4d57-51a4fe1dd9b9@simark.ca> (raw)
In-Reply-To: <87k045ce2d.fsf@tromey.com>

On 11/8/22 16:48, Tom Tromey wrote:
> Simon> Oops, forgot.  Does that look good to you?
> 
> Yes, thank you.
> 
> Tom

Thanks, pushed both patches.

Simon

      reply	other threads:[~2022-11-08 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 15:51 Simon Marchi
2022-11-04 15:51 ` [PATCH 2/2] gdb/linux-nat: get core count using /sys/devices/system/cpu/possible Simon Marchi
2022-11-08 17:17   ` Tom Tromey
2022-11-08 17:13 ` [PATCH 1/2] gdbsupport, gdb: add read_text_file_to_string, use it in linux_common_core_of_thread Tom Tromey
2022-11-08 20:36   ` Simon Marchi
2022-11-08 21:48     ` Tom Tromey
2022-11-08 21:52       ` Simon Marchi [this message]

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=33e56032-0f42-84c5-4d57-51a4fe1dd9b9@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    --cc=tom@tromey.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).