From: Mario Limonciello <mario.limonciello@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the pci tree
Date: Thu, 24 Oct 2024 16:21:28 -0500 [thread overview]
Message-ID: <bef548ce-edfb-49c5-89f9-b77e8cd8692f@amd.com> (raw)
In-Reply-To: <20241025081022.5af39f10@canb.auug.org.au>
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@canb.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.
next prev parent reply other threads:[~2024-10-24 21:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 21:08 linux-next: Fixes tag needs some work in the pci tree Stephen Rothwell
2024-10-24 21:10 ` Stephen Rothwell
2024-10-24 21:21 ` Mario Limonciello [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-30 23:13 Stephen Rothwell
2024-07-01 7:55 ` Niklas Cassel
2024-07-01 20:18 ` Krzysztof Wilczyński
2023-01-15 21:14 Stephen Rothwell
2023-01-16 3:23 ` Alexey V. Vissarionov
2023-01-18 17:06 ` Bjorn Helgaas
2020-11-22 9:55 Stephen Rothwell
2020-11-22 15:13 ` Bjorn Helgaas
2020-07-22 0:33 Stephen Rothwell
2020-03-30 20:38 Stephen Rothwell
2020-03-30 20:53 ` Bjorn Helgaas
2020-03-31 3:14 ` Lukas Wunner
2020-03-31 3:32 ` Lukas Wunner
2020-03-31 15:32 ` Bjorn Helgaas
2019-06-22 13:40 Stephen Rothwell
2019-06-26 10:00 ` Lorenzo Pieralisi
2019-06-26 14:51 ` Bharat Kumar Gogada
2019-02-12 23:03 Stephen Rothwell
2019-02-13 9:55 ` Lorenzo Pieralisi
2019-02-13 14:31 ` Bjorn Helgaas
2019-02-13 20:09 ` Stephen Rothwell
2019-02-13 20:19 ` Bjorn Helgaas
2019-02-13 21:17 ` 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=bef548ce-edfb-49c5-89f9-b77e8cd8692f@amd.com \
--to=mario.limonciello@amd.com \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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