From: Mario Limonciello <mario.limonciello@amd•com>
To: "Rafael J. Wysocki" <rjw@rjwysocki•net>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Dhananjay Ugwekar <Dhananjay.Ugwekar@amd•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
"Gautham R. Shenoy" <gautham.shenoy@amd•com>
Subject: Re: linux-next: Fixes tag needs some work in the pm tree
Date: Thu, 6 Mar 2025 10:54:29 -0600 [thread overview]
Message-ID: <2a21b54a-fe2a-48ab-8d22-0f8a7e6b02e5@amd.com> (raw)
In-Reply-To: <5011851.31r3eYUQgx@rjwysocki.net>
On 3/6/2025 10:52, Rafael J. Wysocki wrote:
> On Thursday, March 6, 2025 7:15:57 AM CET Dhananjay Ugwekar wrote:
>> Hello Stephen,
>>
>> On 3/6/2025 2:58 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> In commit
>>>
>>> f6c0b7602909 ("cpufreq/amd-pstate: Fix the clamping of perf values")
>>>
>>> Fixes tag
>>>
>>> Fixes: 305621eb6a8b ("cpufreq/amd-pstate: Modularize perf<->freq conversion")
>>>
>>> has these problem(s):
>>>
>>> - Target SHA1 does not exist
>>>
>>> Maybe you meant
>>>
>>> Fixes: 620136ced35a ("cpufreq/amd-pstate: Modularize perf<->freq conversion")
>>
>> Yes, you're right, I was referring to that commit,
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=620136ced35a9329f4d1ea90e51bee2dfd7ee5b0
>>
>> Rafael, will you be able to fix the tag it in your tree?, or should I send the amended patch separately?
>
> No, I'm not, this was pulled from Mario.
>
> Mario, can you please fix this and send a new pull request to me for the
> same material?
>
> Thanks!
>
>
>
The tag WAS right originally, but I the sha changed when I rebased on a
later RC and I still had the old sha in my tree so I missed it.
I'll make a replacement tag for you and you can repull.
Thanks,
next prev parent reply other threads:[~2025-03-06 16:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 21:28 linux-next: Fixes tag needs some work in the pm tree Stephen Rothwell
2025-03-06 6:15 ` Dhananjay Ugwekar
2025-03-06 16:52 ` Rafael J. Wysocki
2025-03-06 16:54 ` Mario Limonciello [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-29 22:53 Stephen Rothwell
2025-04-30 18:44 ` Rafael J. Wysocki
2025-04-13 22:33 Stephen Rothwell
2024-12-11 20:43 Stephen Rothwell
2024-03-06 22:05 Stephen Rothwell
2024-02-25 21:38 Stephen Rothwell
2023-01-24 20:42 Stephen Rothwell
2023-01-11 21:16 Stephen Rothwell
2022-10-16 3:44 Stephen Rothwell
2022-05-19 23:02 Stephen Rothwell
2021-04-07 22:38 Stephen Rothwell
2021-04-08 7:52 ` Vitaly Kuznetsov
2020-08-19 22:01 Stephen Rothwell
2020-08-20 4:55 ` Viresh Kumar
2020-03-04 20:53 Stephen Rothwell
2019-12-17 20:17 Stephen Rothwell
2019-10-14 20:59 Stephen Rothwell
2019-10-15 10:08 ` Rafael J. Wysocki
2019-09-10 14:33 Stephen Rothwell
2019-09-11 7:27 ` Heikki Krogerus
2019-09-11 17:17 ` Rafael J. Wysocki
2019-09-12 7:40 ` Heikki Krogerus
2019-07-10 11:26 Stephen Rothwell
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=2a21b54a-fe2a-48ab-8d22-0f8a7e6b02e5@amd.com \
--to=mario.limonciello@amd$(echo .)com \
--cc=Dhananjay.Ugwekar@amd$(echo .)com \
--cc=gautham.shenoy@amd$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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