From: Nick Clifton <nickc@redhat.com>
To: Tom Tromey <tom@tromey.com>, binutils@sourceware.org
Subject: Re: [PATCH v2 0/3] Minimal thread-safety for BFD
Date: Tue, 7 Nov 2023 11:00:40 +0000 [thread overview]
Message-ID: <5e166c6f-b5be-4e02-b45c-244f761f6cf2@redhat.com> (raw)
In-Reply-To: <20231103234355.2012158-1-tom@tromey.com>
Hi Tom,
> Here's v2 of the series to add minimal thread-safety to BFD. I
> believe this version makes all the requested changes.
Patch series approved - please apply. (And thanks for doing this!)
Cheers
Nick
prev parent reply other threads:[~2023-11-07 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 23:43 Tom Tromey
2023-11-03 23:43 ` [PATCH v2 1/3] Make _bfd_error_buf static Tom Tromey
2023-11-03 23:43 ` [PATCH v2 2/3] Make various error-related globals thread-local Tom Tromey
2023-11-03 23:43 ` [PATCH v2 3/3] Add minimal thread-safety to BFD Tom Tromey
2023-11-07 11:00 ` Nick Clifton [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=5e166c6f-b5be-4e02-b45c-244f761f6cf2@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--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).