From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Frank Wunderlich <frank-w@public-files.de>
Cc: linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: regression with 33140e668b10 thermal/drivers/mediatek: Control buffer enablement tweaks
Date: Tue, 12 Sep 2023 14:23:06 +0200 [thread overview]
Message-ID: <e264149e-c053-4346-a645-e694ed791569@leemhuis.info> (raw)
In-Reply-To: <ZPBjGWPjSfl-HmDJ@debian.me>
[TLDR: This mail in primarily relevant for Linux regression tracking. A
change or fix related to the regression discussed in this thread was
posted or applied, but it did not use a Closes: tag to point to the
report, as Linus and the documentation call for. Things happen, no
worries -- but now the regression tracking bot needs to be told manually
about the fix. See link in footer if these mails annoy you.]
On 31.08.23 11:53, Bagas Sanjaya wrote:
> On Thu, Aug 31, 2023 at 11:25:11AM +0200, Frank Wunderlich wrote:
>>
>> The commit 33140e668b10 "thermal/drivers/mediatek: Control buffer enablement tweaks" is merged between 6.3 and 6.4 and causes a regression where temperature cannot be read correctly at least for mt7986/Bpi-R3.
>>
>> bpi-r3 ~ # cat /sys/class/thermal/thermal_zone0/temp
>> -274000
>>
>> after reverting the commit and fixing some build-errors in 6.5-rc7 because new members used in mt8365_thermal_data too, we can read temperature on mt7986 again.
>>
>
> Thanks for the regression report. I'm adding it to regzbot:
>
> #regzbot ^introduced: 33140e668b1020
> #regzbot title: incorrect temperature on MT7986 due to tweaking buffer
#regzbot monitor:
https://lore.kernel.org/all/20230907112018.52811-1-linux@fw-web.de/
#regzbot fix: thermal/drivers/mediatek: Fix control buffer enablement on
MT7896
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-09-12 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 9:25 regression with 33140e668b10 thermal/drivers/mediatek: Control buffer enablement tweaks Frank Wunderlich
2023-08-31 9:53 ` Bagas Sanjaya
2023-09-12 12:23 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
2023-11-01 11:03 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-31 13:34 ` Aw: " Frank Wunderlich
2023-09-12 12:57 ` Daniel Lezcano
2023-09-12 13:46 ` Markus Schneider-Pargmann
2023-09-12 20:38 ` Frank Wunderlich
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=e264149e-c053-4346-a645-e694ed791569@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=frank-w@public-files.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=regressions@lists.linux.dev \
/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