From: Greg KH <gregkh@linuxfoundation.org>
To: Guoqing Jiang <guoqing.jiang@linux.dev>
Cc: stable@vger.kernel.org
Subject: Re: question about one acpi-cpufreq commit
Date: Wed, 16 Mar 2022 13:53:07 +0100 [thread overview]
Message-ID: <YjHds8pwnJh1VvX6@kroah.com> (raw)
In-Reply-To: <725da4b6-8ce8-d2d1-a9ce-cd8ca2e89fee@linux.dev>
On Wed, Mar 16, 2022 at 08:42:56PM +0800, Guoqing Jiang wrote:
>
>
> On 3/16/22 7:02 PM, Greg KH wrote:
> > On Wed, Mar 16, 2022 at 04:56:11PM +0800, Guoqing Jiang wrote:
> > > Hi,
> > >
> > > I just found the commit in 5.10 stable kernel.
> > >
> > > stable-linux> git tag --sort=taggerdate --contain
> > > 8a3fc32b322cc3081dd3569047c9834f496b4ab0 | head -1
> > > v5.10.17
> > >
> > > commit 8a3fc32b322cc3081dd3569047c9834f496b4ab0
> > > Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > Date: Thu Feb 4 18:25:37 2021 +0100
> > >
> > > cpufreq: ACPI: Extend frequency tables to cover boost frequencies
> > >
> > > commit 3c55e94c0adea4a5389c4b80f6ae9927dd6a4501 upstream.
> > >
> > > [ ... ]
> > >
> > > Fixes: 41ea667227ba ("x86, sched: Calculate frequency invariance for AMD
> > > systems")
> > > Fixes: 976df7e5730e ("x86, sched: Use midpoint of max_boost and max_P
> > > for frequency invariance on AMD EPYC")
> > > Fixes: db865272d9c4 ("cpufreq: Avoid configuring old governors as
> > > default with intel_pstate")
> > >
> > > Except db865272d9c4 was applied in v5.10-rc2, the others (41ea667227ba and
> > > 976df7e5730e)
> > > were first appeared in v5.11-rc1.
> > >
> > > linux> git tag --sort=taggerdate --contain 41ea667227ba | head -1
> > > v5.11-rc1
> > > linux> git tag --sort=taggerdate --contain 976df7e5730e | head -1
> > > v5.11-rc1
> > > linux> git tag --sort=taggerdate --contain db865272d9c4 | head -1
> > > v5.10-rc2
> > >
> > > So I am wondering if the mentioned commit is suitable for 5.10 stable
> > > kernel, or what am I missing?
> > Is it causing a problem for you? What is the issue with having it in
> > the 5.10.y tree?
>
> No.
>
> I am trying to port 41ea667227ba and relevant commits to our kernel which
> is based on 5.10 stable kernel, and I am being asked to port 3c55e94c0ade
> per the fix tag after 41ea667227ba was added, then I was confused because
> of conflict.
Don't "port" stable kernels, just do a normal merge and then all is much
better. That way you do not miss patches you should have applied but
didn't realize until much later...
good luck!
greg k-h
next prev parent reply other threads:[~2022-03-16 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 8:56 question about one acpi-cpufreq commit Guoqing Jiang
2022-03-16 11:02 ` Greg KH
2022-03-16 12:42 ` Guoqing Jiang
2022-03-16 12:53 ` Greg KH [this message]
2022-03-17 11:46 ` Guoqing Jiang
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=YjHds8pwnJh1VvX6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=guoqing.jiang@linux.dev \
--cc=stable@vger.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.