public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Lancelot SIX <lancelot.six@amd.com>
Cc: Tom Tromey <tromey@adacore.com>,  <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 0/7] Rewrite gdb_bfd_openr_iovec to be type-safe
Date: Thu, 28 Sep 2023 10:45:54 -0600	[thread overview]
Message-ID: <87v8bu2qm5.fsf@tromey.com> (raw)
In-Reply-To: <20230928100223.o6nve3z3vrv4wv2s@hpe6u-23> (Lancelot SIX's message of "Thu, 28 Sep 2023 10:02:23 +0000")

>>>>> "Lancelot" == Lancelot SIX <lancelot.six@amd.com> writes:

Lancelot> Hi Tom,
Lancelot> I went through the series and tested it locally (native boald against
Lancelot> master and downstream ROCgdb).

Lancelot> Reviewed-By: Lancelot Six <lancelot.six@amd.com>

Thank you, I'm going to check this in.

Tom

      reply	other threads:[~2023-09-28 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 14:52 Tom Tromey
2023-09-18 14:52 ` [PATCH v2 1/7] Introduce type-safe variant of gdb_bfd_openr_iovec Tom Tromey
2023-09-18 14:52 ` [PATCH v2 2/7] Small constructor change to target_buffer Tom Tromey
2023-09-18 14:52 ` [PATCH v2 3/7] Convert mem_bfd_iovec to new type-safe gdb_bfd_openr_iovec Tom Tromey
2023-09-18 14:52 ` [PATCH v2 4/7] Convert target fileio " Tom Tromey
2023-09-18 14:52 ` [PATCH v2 5/7] Convert minidebug " Tom Tromey
2023-09-18 14:52 ` [PATCH v2 6/7] Convert solib-rocm " Tom Tromey
2023-09-28  9:57   ` Lancelot SIX
2023-09-18 14:52 ` [PATCH v2 7/7] Remove old gdb_bfd_openr_iovec Tom Tromey
2023-09-28 10:02 ` [PATCH v2 0/7] Rewrite gdb_bfd_openr_iovec to be type-safe Lancelot SIX
2023-09-28 16:45   ` Tom Tromey [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=87v8bu2qm5.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lancelot.six@amd.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).