From: Brady Norander <bradynorander@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, alexander.deucher@amd.com,
christian.koenig@amd.com, airlied@gmail.com, simona@ffwll.ch,
sunil.khatri@amd.com, boyuan.zhang@amd.com
Subject: Re: [PATCH] drm/amdgpu: use static ids for ACP platform devs
Date: Mon, 10 Nov 2025 19:17:31 -0500 [thread overview]
Message-ID: <13627c6c-f428-4520-b0d4-32fca1e7a2a0@gmail.com> (raw)
In-Reply-To: <CADnq5_No+w+tco9j35GBM3+CYBTo018eLwWec278d3VBJHPQxw@mail.gmail.com>
On 11/10/25 14:14, Alex Deucher wrote:
> On Tue, Mar 25, 2025 at 7:11 PM Brady Norander <bradynorander@gmail.com> wrote:
>>
>> On 3/25/25 6:12 PM, Alex Deucher wrote:
>>>
>>> While you are at it, can you take a look at
>>> drivers/gpu/drm/amd/amdgpu/isp_v4_1_0.c and
>>> drivers/gpu/drm/amd/amdgpu/isp_v4_1_1.c as well?
>>>
>>> Alex
>>
>> I think it makes more sense to handle that in a separate patch as it is
>> an unrelated ip block.
>
> Sure. Can you send a patch to fix those up as well if needed?
>
> Alex
I don't know if that driver needs this, and I also don't have that
hardware to test it. If that driver needs this fix, then this can be
revisited but I don't think it should block this patch being merged now.
next prev parent reply other threads:[~2025-11-11 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 21:05 [PATCH] drm/amdgpu: use static ids for ACP platform devs Brady Norander
2025-03-25 22:12 ` Alex Deucher
2025-03-25 23:11 ` Brady Norander
2025-11-10 19:14 ` Alex Deucher
2025-11-11 0:17 ` Brady Norander [this message]
2025-11-30 13:48 ` Brady Norander
2025-12-01 18:13 ` Alex Deucher
2025-11-10 7:28 ` Oleksandr Natalenko
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=13627c6c-f428-4520-b0d4-32fca1e7a2a0@gmail.com \
--to=bradynorander@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=boyuan.zhang@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=sunil.khatri@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