From: "Six, Lancelot" <Lancelot.Six@amd.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] Avoid race when reading dwz file
Date: Sat, 30 Mar 2024 16:47:25 +0000 [thread overview]
Message-ID: <CH3PR12MB90790055DA37C61DF215E1A883392@CH3PR12MB9079.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87edbuq7qg.fsf@tromey.com>
[AMD Official Use Only - General]
> I think that would be fine. I'm happy to do it if you'd rather.
>
> thanks,
> Tom
Hi,
I have submitted https://sourceware.org/pipermail/gdb-patches/2024-March/207682.html. Let me know what you think.
Thanks,
Lancelot.
prev parent reply other threads:[~2024-03-30 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:51 Tom Tromey
2024-03-08 14:09 ` Tom Tromey
2024-03-28 10:37 ` Lancelot SIX
2024-03-28 23:03 ` Tom Tromey
2024-03-30 16:47 ` Six, Lancelot [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=CH3PR12MB90790055DA37C61DF215E1A883392@CH3PR12MB9079.namprd12.prod.outlook.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@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