Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Fix some trivial build failures with clang
Date: Mon, 25 Mar 2024 18:33:37 -0600	[thread overview]
Message-ID: <87plvhrfvi.fsf@tromey.com> (raw)
In-Reply-To: <20240325183011.1037710-1-simon.marchi@efficios.com> (Simon Marchi's message of "Mon, 25 Mar 2024 14:27:58 -0400")

>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:

Simon> Fix two trivial build failures when building with Clang.  I see more
Simon> problems, but they were not as trivial, so I'm leaving them for another
Simon> patch series.

Thanks.
Approved-By: Tom Tromey <tom@tromey.com>

Tom

  parent reply	other threads:[~2024-03-26  0:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 18:27 Simon Marchi
2024-03-25 18:27 ` [PATCH 1/2] gdb: mark addrmap classes `final` Simon Marchi
2024-03-25 18:28 ` [PATCH 2/2] gdbserver/Makefile.in: add missing `-x c++` Simon Marchi
2024-03-26  0:33 ` Tom Tromey [this message]
2024-03-26  1:49   ` [PATCH 0/2] Fix some trivial build failures with clang 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=87plvhrfvi.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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