From: Guinevere Larsen <guinevere@redhat.com>
To: Simon Marchi <simark@simark.ca>,
Simon Marchi <simon.marchi@polymtl.ca>,
Lancelot SIX <Lancelot.Six@amd.com>,
gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 1/3] gdb/amd-dbgapi: use gdb::unordered_map
Date: Wed, 15 Jan 2025 15:50:12 -0300 [thread overview]
Message-ID: <da007d8a-e91c-496f-93ec-fbb037421542@redhat.com> (raw)
In-Reply-To: <49b2c439-b459-480c-9918-64344424c5b6@simark.ca>
On 1/15/25 3:46 PM, Simon Marchi wrote:
>
> On 2025-01-15 13:41, Simon Marchi wrote:
>>
>> On 2025-01-15 05:55, Lancelot SIX wrote:
>>>
>>> On 14/01/2025 19:16, simon.marchi@polymtl.ca wrote:
>>>> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>>>>
>>>>
>>>> From: Simon Marchi <simon.marchi@efficios.com>
>>>>
>>>> Since we have gdb::unordered_map, swap std::unordered_map for that.
>>>>
>>> Hi,
>>>
>>> That looks good to me, thanks.
>>>
>>> Since it only touches the amdgpu backend,
>>> Approved-By: Lancelot Six <lancelot.six@amd.com> (amdgpu)
>> Thanks, added.
>>
>> Is the (amdgpu) some format we use? I haven't seen it used anywhere
>> else. I don't mind, for instance, Eli could use Approved-By with (doc).
It was the thing we agreed on when I added the trailer information to
the maintainers file. The examples specifically use a comma separated
list of areas in parenthesis after the tag.
> Just note that `b4 am` doesn't preserve the parenthesis, so it's not so
> handy actually.
>
> Simon
>
Ah, that's unfortunate. We might want to update that format then, but we
should also update the maintainers file
--
Cheers,
Guinevere Larsen
She/Her/Hers
next prev parent reply other threads:[~2025-01-15 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 19:16 [PATCH 0/3] Add displaced stepping support for AMD GPUs simon.marchi
2025-01-14 19:16 ` [PATCH 1/3] gdb/amd-dbgapi: use gdb::unordered_map simon.marchi
2025-01-15 10:55 ` Lancelot SIX
2025-01-15 18:41 ` Simon Marchi
2025-01-15 18:46 ` Simon Marchi
2025-01-15 18:50 ` Guinevere Larsen [this message]
2025-01-15 18:55 ` Lancelot SIX
2025-01-14 19:16 ` [PATCH 2/3] gdb: add target displaced stepping support simon.marchi
2025-01-14 19:16 ` [PATCH 3/3] gdb/amd-dbgapi: add " simon.marchi
2025-01-15 11:02 ` Lancelot SIX
2025-01-15 18:45 ` Simon Marchi
2025-02-25 17:17 ` 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=da007d8a-e91c-496f-93ec-fbb037421542@redhat.com \
--to=guinevere@redhat.com \
--cc=Lancelot.Six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.com \
--cc=simon.marchi@polymtl.ca \
/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