From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9006CC433F5 for ; Thu, 17 Mar 2022 11:46:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233113AbiCQLr4 (ORCPT ); Thu, 17 Mar 2022 07:47:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52886 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233159AbiCQLry (ORCPT ); Thu, 17 Mar 2022 07:47:54 -0400 Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51D251D2050 for ; Thu, 17 Mar 2022 04:46:37 -0700 (PDT) Subject: Re: question about one acpi-cpufreq commit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1647517594; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pAVhBHPBPQvox4tJtK2J7fSLXD8VsjgglLOI5McB40s=; b=jatMAMsOKHbtjdPWPrUpdfatA3a/ukne2s3HpneTSkyA9tKA/YYZ+tSDyy1+84IMzW/Ho8 yE+oxE6AvJZzpQiKk4BIQWeI0zNDhYk1zBHYZ4ClMNqmgq2UC7ymyw792In6neWFFncLtO cPBONIyHPzunUf221ImllS1FlUSrWx4= To: Greg KH Cc: stable@vger.kernel.org References: <87723ab6-2aa7-cf7f-0e91-38a35b29f92b@linux.dev> <725da4b6-8ce8-d2d1-a9ce-cd8ca2e89fee@linux.dev> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Guoqing Jiang Message-ID: <9df26263-aa57-ed09-1b8f-bc2cd2fe0dc5@linux.dev> Date: Thu, 17 Mar 2022 19:46:30 +0800 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: linux.dev Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On 3/16/22 8:53 PM, Greg KH wrote: > 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 >>>> 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... Thanks for the tip and also the effort for stable kernel maintenance! Thanks, Guoqing