From: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
To: alexdeucher@gmail.com
Cc: 062bel313@gmail.com, Alexander.Deucher@amd.com,
Christian.Koenig@amd.com, Kenneth.Feng@amd.com,
airlied@gmail.com, amd-gfx@lists.freedesktop.org,
atharvatiwarilinuxdev@gmail.com, dri-devel@lists.freedesktop.org,
ed@aicharmers.com, linux-kernel@vger.kernel.org, simona@ffwll.ch
Subject: Re: [PATCH v2] drm/amd/pm: defer UCLK DPM enablement on Apple Navi 14
Date: Sat, 12 Sep 2026 20:50:48 -0400 [thread overview]
Message-ID: <20260913005048.1167-1-atharvatiwarilinuxdev@gmail.com> (raw)
In-Reply-To: <CADnq5_PNt5Huo-bk=tqdCLorUp3BDCtdGmaFJDxfVbcKx-CPoQ@mail.gmail.com>
> Applied. Thanks!
Hey, so im the author of the original patch:
https://github.com/t2linux/wiki/issues/743#issuecomment-5347204171
The author of the patch mentions this:
> Combine Atharva Tiwari's delayed-UCLK proposal for 0219 with the Navi post-init implementation for 0218. Retain the revision restriction for
> 0218 and the revision-independent 0219 match from Atharva's proposal.
So as the main developer of the patch, i would like you to remove this patch,
as it dosent give me credit, and also this is not the solution to this problem
as i have mentioned here:
https://github.com/t2linux/wiki/issues/743#issuecomment-5608044095
thanks
prev parent reply other threads:[~2026-09-13 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 19:04 [PATCH] drm/amdgpu/smu: Enable UCLK after init in AMD Radeon Pro 5300 Atharva Tiwari
2026-09-09 7:05 ` Feng, Kenneth
2026-09-09 7:35 ` Ed Schofield
2026-09-09 8:02 ` Ed Schofield
2026-09-09 8:39 ` Feng, Kenneth
2026-09-09 12:34 ` [PATCH v2] drm/amd/pm: defer UCLK DPM enablement on Apple Navi 14 Ed Schofield
2026-09-10 10:31 ` Feng, Kenneth
2026-09-10 13:21 ` Alex Deucher
2026-09-13 0:50 ` Atharva Tiwari [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=20260913005048.1167-1-atharvatiwarilinuxdev@gmail.com \
--to=atharvatiwarilinuxdev@gmail.com \
--cc=062bel313@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Kenneth.Feng@amd.com \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ed@aicharmers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.