[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bef548ce-edfb-49c5-89f9-b77e8cd8692f@amd.com>
Date: Thu, 24 Oct 2024 16:21:28 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof WilczyĆski <kw@...ux.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the pci tree
On 10/24/2024 16:10, Stephen Rothwell wrote:
> Hi all,
>
> Sorry, this should have referred to the pm tree not he pci tree.
>
> On Fri, 25 Oct 2024 08:08:00 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>> In commit
>>
>> 7027b415ff1a ("cpufreq/amd-pstate-ut: Add fix for min freq unit test")
>>
>> Fixes tag
>>
>> Fixes: 642aff3964b0f ("cpufreq/amd-pstate: Set the initial min_freq to lowest_nonlinear_freq")
>>
>> has these problem(s):
>>
>> - Target SHA1 does not exist
>>
>> Maybe you meant
>>
>> Fixes: f2542c904294 ("cpufreq/amd-pstate: Set the initial min_freq to lowest_nonlinear_freq")
>
Ah, this happened because we did a rebase to drop out some patches
pulled in prematurely the commit IDs changed for stuff on top. Both
commits are coming in 6.13-rc1 so there is no impact to stable trees, I
guess it's OK if the commit log has a mistake.
Powered by blists - more mailing lists