All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"vincent@systemli.org" <vincent@systemli.org>,
	"frank-w@public-files.de" <frank-w@public-files.de>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"Jia-wei Chang (張佳偉)" <Jia-wei.Chang@mediatek.com>,
	"Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>,
	"thomas.huehn@hs-nordhausen.de" <thomas.huehn@hs-nordhausen.de>,
	"daniel@makrotopia.org" <daniel@makrotopia.org>
Subject: Re: Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622)
Date: Fri, 2 Dec 2022 11:51:11 +0100	[thread overview]
Message-ID: <13e87195-69b0-da11-b039-441dab3ef4c8@leemhuis.info> (raw)
In-Reply-To: <20221202104731.63mfshxwu3mqlbli@vireshk-i7>

On 02.12.22 11:47, Viresh Kumar wrote:
> On 02-12-22, 11:41, Thorsten Leemhuis wrote:
>> Quick question: is that relative to apply at this point of the 6.1 devel
>> cycle? Or would it be better to revert the culprit (already introduced
>> in 5.19) for now and reapply it together with that fix for 6.2 (and then
>> backport to 6.1 stable later)?
> 
> I am not comfortable applying the revert to 6.1 kernel right now, it
> is too late and the revert is big enough. Also it isn't something that
> came in 6.1 cycle itself, so it isn't ideal to merge it as a fix this
> late.
> 
> I would like to apply the fix, if we are able to settle on one, for
> 6.2 and let it get backported via stable to all the affected kernels.

Okay, thx, fine for me, just was wondering how to best handle this.

Ciao, Thorsten


WARNING: multiple messages have this Message-ID (diff)
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"daniel@makrotopia.org" <daniel@makrotopia.org>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
	"thomas.huehn@hs-nordhausen.de" <thomas.huehn@hs-nordhausen.de>,
	"Jia-wei Chang (張佳偉)" <Jia-wei.Chang@mediatek.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"vincent@systemli.org" <vincent@systemli.org>
Subject: Re: Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622)
Date: Fri, 2 Dec 2022 11:51:11 +0100	[thread overview]
Message-ID: <13e87195-69b0-da11-b039-441dab3ef4c8@leemhuis.info> (raw)
In-Reply-To: <20221202104731.63mfshxwu3mqlbli@vireshk-i7>

On 02.12.22 11:47, Viresh Kumar wrote:
> On 02-12-22, 11:41, Thorsten Leemhuis wrote:
>> Quick question: is that relative to apply at this point of the 6.1 devel
>> cycle? Or would it be better to revert the culprit (already introduced
>> in 5.19) for now and reapply it together with that fix for 6.2 (and then
>> backport to 6.1 stable later)?
> 
> I am not comfortable applying the revert to 6.1 kernel right now, it
> is too late and the revert is big enough. Also it isn't something that
> came in 6.1 cycle itself, so it isn't ideal to merge it as a fix this
> late.
> 
> I would like to apply the fix, if we are able to settle on one, for
> 6.2 and let it get backported via stable to all the affected kernels.

Okay, thx, fine for me, just was wondering how to best handle this.

Ciao, Thorsten



WARNING: multiple messages have this Message-ID (diff)
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"vincent@systemli.org" <vincent@systemli.org>,
	"frank-w@public-files.de" <frank-w@public-files.de>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"Jia-wei Chang (張佳偉)" <Jia-wei.Chang@mediatek.com>,
	"Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>,
	"thomas.huehn@hs-nordhausen.de" <thomas.huehn@hs-nordhausen.de>,
	"daniel@makrotopia.org" <daniel@makrotopia.org>
Subject: Re: Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622)
Date: Fri, 2 Dec 2022 11:51:11 +0100	[thread overview]
Message-ID: <13e87195-69b0-da11-b039-441dab3ef4c8@leemhuis.info> (raw)
In-Reply-To: <20221202104731.63mfshxwu3mqlbli@vireshk-i7>

On 02.12.22 11:47, Viresh Kumar wrote:
> On 02-12-22, 11:41, Thorsten Leemhuis wrote:
>> Quick question: is that relative to apply at this point of the 6.1 devel
>> cycle? Or would it be better to revert the culprit (already introduced
>> in 5.19) for now and reapply it together with that fix for 6.2 (and then
>> backport to 6.1 stable later)?
> 
> I am not comfortable applying the revert to 6.1 kernel right now, it
> is too late and the revert is big enough. Also it isn't something that
> came in 6.1 cycle itself, so it isn't ideal to merge it as a fix this
> late.
> 
> I would like to apply the fix, if we are able to settle on one, for
> 6.2 and let it get backported via stable to all the affected kernels.

Okay, thx, fine for me, just was wondering how to best handle this.

Ciao, Thorsten


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-12-02 10:51 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 13:35 Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) Nick
2022-11-09 13:35 ` Nick
2022-11-09 19:40 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) #forregzbot Thorsten Leemhuis
2022-11-09 19:40   ` Thorsten Leemhuis
2022-11-10 11:26 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) Matthias Brugger
2022-11-10 11:26   ` Matthias Brugger
2022-11-15 19:44   ` Nick
2022-11-15 19:44     ` Nick
2022-12-01 15:08     ` Thorsten Leemhuis
2022-12-01 15:08       ` Thorsten Leemhuis
2022-12-01 15:26       ` Daniel Golle
2022-12-01 15:26         ` Daniel Golle
2022-12-01 15:26         ` Daniel Golle
2022-12-01 15:39         ` Thorsten Leemhuis
2022-12-01 15:39           ` Thorsten Leemhuis
2022-12-01 15:39           ` Thorsten Leemhuis
2022-12-01 21:40           ` Nick
2022-12-01 21:40             ` Nick
2022-12-01 21:40             ` Nick
2022-12-02  5:27           ` Viresh Kumar
2022-12-02  5:27             ` Viresh Kumar
2022-12-02  5:27             ` Viresh Kumar
2022-12-02  8:57             ` AngeloGioacchino Del Regno
2022-12-02  8:57               ` AngeloGioacchino Del Regno
2022-12-02  8:57               ` AngeloGioacchino Del Regno
2022-12-02  9:19               ` AngeloGioacchino Del Regno
2022-12-02  9:19                 ` AngeloGioacchino Del Regno
2022-12-02  9:19                 ` AngeloGioacchino Del Regno
2022-12-02  9:43                 ` Allen-KH Cheng (程冠勳)
2022-12-02  9:43                   ` Allen-KH Cheng (程冠勳)
2022-12-02  9:43                   ` Allen-KH Cheng (程冠勳)
2022-12-02 10:02                   ` AngeloGioacchino Del Regno
2022-12-02 10:02                     ` AngeloGioacchino Del Regno
2022-12-02 10:02                     ` AngeloGioacchino Del Regno
2022-12-02 10:41                     ` Thorsten Leemhuis
2022-12-02 10:41                       ` Thorsten Leemhuis
2022-12-02 10:41                       ` Thorsten Leemhuis
2022-12-02 10:47                       ` Viresh Kumar
2022-12-02 10:47                         ` Viresh Kumar
2022-12-02 10:47                         ` Viresh Kumar
2022-12-02 10:51                         ` Thorsten Leemhuis [this message]
2022-12-02 10:51                           ` Thorsten Leemhuis
2022-12-02 10:51                           ` Thorsten Leemhuis
2022-12-02 11:00                       ` AngeloGioacchino Del Regno
2022-12-02 11:00                         ` AngeloGioacchino Del Regno
2022-12-02 11:00                         ` AngeloGioacchino Del Regno
2022-12-02 11:01                         ` Viresh Kumar
2022-12-02 11:01                           ` Viresh Kumar
2022-12-02 11:01                           ` Viresh Kumar
2022-12-07 15:34                           ` Nick
2022-12-07 15:34                             ` Nick
2022-12-07 15:34                             ` Nick
2022-12-19 12:21                             ` Allen-KH Cheng (程冠勳)
2022-12-19 12:21                               ` Allen-KH Cheng (程冠勳)
2022-12-20 14:37                               ` Nick
2022-12-20 14:37                                 ` Nick
2022-12-21  9:24                                 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) #forregzbot Thorsten Leemhuis
2022-12-21  9:24                                   ` Thorsten Leemhuis
2022-12-02 12:25                       ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) Nick
2022-12-02 12:25                         ` Nick
2022-12-02 12:25                         ` Nick
2022-12-02  5:26 ` [PATCH] Revert "cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()" Viresh Kumar
2022-12-02  5:26   ` Viresh Kumar
2022-12-02 12:17   ` Rafael J. Wysocki
2022-12-02 12:17     ` Rafael J. Wysocki
2022-12-02 19:46     ` Rafael J. Wysocki
2022-12-02 19:46       ` Rafael J. Wysocki
2022-12-05  4:30       ` Viresh Kumar
2022-12-05  4:30         ` Viresh Kumar
2022-12-05 12:08         ` Rafael J. Wysocki
2022-12-05 12:08           ` Rafael J. Wysocki
2022-12-05 23:30           ` Viresh Kumar
2022-12-05 23:30             ` Viresh Kumar
2022-12-02 12:47   ` Nick
2022-12-02 12:47     ` Nick

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=13e87195-69b0-da11-b039-441dab3ef4c8@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=Allen-KH.Cheng@mediatek.com \
    --cc=Jia-wei.Chang@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=Rex-BC.Chen@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=daniel@makrotopia.org \
    --cc=frank-w@public-files.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=thomas.huehn@hs-nordhausen.de \
    --cc=vincent@systemli.org \
    --cc=viresh.kumar@linaro.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.