From: Nick <vincent@systemli.org>
To: "Thorsten Leemhuis" <regressions@leemhuis.info>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>
Cc: "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>,
"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 13:25:31 +0100 [thread overview]
Message-ID: <cb0f0500-fb8a-2a01-1dd4-ab50714f595a@systemli.org> (raw)
In-Reply-To: <c186d104-43e0-ca10-3ce2-c2f922acd8bf@leemhuis.info>
On 12/2/22 11:41, Thorsten Leemhuis wrote:
> Reported-by: Nick<vincent@systemli.org>
You can also use "Reported-by: Nick Hainke <vincent@systemli.org>" ;)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-02 12:26 UTC|newest]
Thread overview: 30+ 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 19:40 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) #forregzbot 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-15 19:44 ` Nick
2022-12-01 15:08 ` Thorsten Leemhuis
2022-12-01 15:26 ` Daniel Golle
2022-12-01 15:39 ` Thorsten Leemhuis
2022-12-01 21:40 ` Nick
2022-12-02 5:27 ` Viresh Kumar
2022-12-02 8:57 ` AngeloGioacchino Del Regno
2022-12-02 9:19 ` AngeloGioacchino Del Regno
2022-12-02 9:43 ` Allen-KH Cheng (程冠勳)
2022-12-02 10:02 ` AngeloGioacchino Del Regno
2022-12-02 10:41 ` Thorsten Leemhuis
2022-12-02 10:47 ` Viresh Kumar
2022-12-02 10:51 ` Thorsten Leemhuis
2022-12-02 11:00 ` AngeloGioacchino Del Regno
2022-12-02 11:01 ` Viresh Kumar
2022-12-07 15:34 ` Nick
2022-12-19 12:21 ` Allen-KH Cheng (程冠勳)
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-02 12:25 ` Nick [this message]
2022-12-02 5:26 ` [PATCH] Revert "cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()" Viresh Kumar
2022-12-02 12:17 ` Rafael J. Wysocki
2022-12-02 19:46 ` Rafael J. Wysocki
2022-12-05 4:30 ` Viresh Kumar
2022-12-05 12:08 ` Rafael J. Wysocki
2022-12-05 23:30 ` Viresh Kumar
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=cb0f0500-fb8a-2a01-1dd4-ab50714f595a@systemli.org \
--to=vincent@systemli.org \
--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@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=thomas.huehn@hs-nordhausen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).