public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Lancelot SIX <Lancelot.Six@amd.com>
To: Tom Tromey <tom@tromey.com>,
	Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Cc: simark@simark.ca, lsix@lancelotsix.com
Subject: Re: [PATCH v3 2/2] gdb: Change psymbol_functions::require_partial_symbols to partial_symbols
Date: Thu, 26 May 2022 21:42:01 +0100	[thread overview]
Message-ID: <80766d16-9003-ff3c-756c-432c4d512e79@amd.com> (raw)
In-Reply-To: <87a6b46utm.fsf@tromey.com>

Hi,

Thanks.

I just pushed the 2 patches.

Best,
Lancelot.

On 26/05/2022 18:57, Tom Tromey wrote:
> [CAUTION: External Email]
> 
>>>>>> "Lancelot" == Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Lancelot> Here is an updated (V3) version of the last patch of the series which
> Lancelot> renames require_partial_symbols into partial_symbols and updates the
> Lancelot> relevant comments.
> 
> FWIW this looks good to me.
> 
> Tom

      reply	other threads:[~2022-05-26 20:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 18:45 [PATCH v2 0/2] Fix regression with lazy-loading of partial symbols Lancelot SIX
2022-05-19 18:45 ` [PATCH v2 1/2] gdb: Require psymtab before calling quick_functions in objfile Lancelot SIX
2022-05-20 15:51   ` Tom Tromey
2022-05-20 23:07     ` Lancelot SIX
2022-05-21  1:07       ` Tom Tromey
2022-05-19 18:45 ` [PATCH v2 2/2] gdb: Simplify psymbol_functions::require_partial_symbols Lancelot SIX
2022-05-20 15:51   ` Tom Tromey
2022-05-20 16:07   ` Simon Marchi
2022-05-20 22:55     ` [PATCH v3 2/2] gdb: Change psymbol_functions::require_partial_symbols to partial_symbols Lancelot SIX
2022-05-26 17:57       ` Tom Tromey
2022-05-26 20:42         ` Lancelot SIX [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=80766d16-9003-ff3c-756c-432c4d512e79@amd.com \
    --to=lancelot.six@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --cc=simark@simark.ca \
    --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).