From: Mario Limonciello <mario.limonciello@amd.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Wolfram Sang <wsa@kernel.org>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH v2 2/2] Revert "drm/amd/pm: workaround for the wrong ac power detection on smu 13.0.0"
Date: Thu, 5 Oct 2023 14:15:21 -0500 [thread overview]
Message-ID: <91ee347e-0654-48f4-b1ea-8cf752cabe20@amd.com> (raw)
In-Reply-To: <2023100547-vitamins-detergent-4d18@gregkh>
On 10/5/2023 14:12, Greg Kroah-Hartman wrote:
> On Thu, Oct 05, 2023 at 12:52:30PM -0500, Mario Limonciello wrote:
>> This reverts commit 0e5e1a84f0b8c814d502a135824244127fed8f23.
>>
>> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>
> No explaination as to why this needs to be reverted? And does this need
> to be backported anywhere?
>
> thanks,
>
> greg k-h
No need to be backported anywhere. The commit is only in
amd-staging-drm-next right now.
I think it's up to whether Alex includes the workaround commit in the
final 6.7 pull request. If he does, then yeah this could use a larger
write up to explain why it went in and out.
I was sort of thinking we could land both commits amd-staging-drm-next
and then when Alex did the pull request the workaround commit just
wouldn't be part of the 6.7 PR since it's a no-op with the revert.
WARNING: multiple messages have this Message-ID (diff)
From: Mario Limonciello <mario.limonciello@amd.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Wolfram Sang <wsa@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Alex Deucher <alexander.deucher@amd.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] Revert "drm/amd/pm: workaround for the wrong ac power detection on smu 13.0.0"
Date: Thu, 5 Oct 2023 14:15:21 -0500 [thread overview]
Message-ID: <91ee347e-0654-48f4-b1ea-8cf752cabe20@amd.com> (raw)
In-Reply-To: <2023100547-vitamins-detergent-4d18@gregkh>
On 10/5/2023 14:12, Greg Kroah-Hartman wrote:
> On Thu, Oct 05, 2023 at 12:52:30PM -0500, Mario Limonciello wrote:
>> This reverts commit 0e5e1a84f0b8c814d502a135824244127fed8f23.
>>
>> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>
> No explaination as to why this needs to be reverted? And does this need
> to be backported anywhere?
>
> thanks,
>
> greg k-h
No need to be backported anywhere. The commit is only in
amd-staging-drm-next right now.
I think it's up to whether Alex includes the workaround commit in the
final 6.7 pull request. If he does, then yeah this could use a larger
write up to explain why it went in and out.
I was sort of thinking we could land both commits amd-staging-drm-next
and then when Alex did the pull request the workaround commit just
wouldn't be part of the 6.7 PR since it's a no-op with the revert.
next prev parent reply other threads:[~2023-10-05 19:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 17:52 [PATCH v2 0/2] Fix Navi3x boot and hotplug problems Mario Limonciello
2023-10-05 17:52 ` Mario Limonciello
2023-10-05 17:52 ` [PATCH v2 1/2] usb: typec: ucsi: Use GET_CAPABILITY attributes data to set power supply scope Mario Limonciello
2023-10-05 17:52 ` Mario Limonciello
2023-10-05 19:13 ` Greg Kroah-Hartman
2023-10-05 19:13 ` Greg Kroah-Hartman
2023-10-05 20:35 ` Sebastian Reichel
2023-10-05 20:35 ` Sebastian Reichel
2023-10-05 17:52 ` [PATCH v2 2/2] Revert "drm/amd/pm: workaround for the wrong ac power detection on smu 13.0.0" Mario Limonciello
2023-10-05 17:52 ` Mario Limonciello
2023-10-05 19:12 ` Greg Kroah-Hartman
2023-10-05 19:12 ` Greg Kroah-Hartman
2023-10-05 19:15 ` Mario Limonciello [this message]
2023-10-05 19:15 ` Mario Limonciello
2023-10-05 19:17 ` Alex Deucher
2023-10-05 19:17 ` Alex Deucher
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=91ee347e-0654-48f4-b1ea-8cf752cabe20@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=wsa@kernel.org \
/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.