All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Johan Hovold <johan@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Lenovo ThinkPad X13s regerssions (was Re: Linux regressions report for mainline [2024-02-25])
Date: Tue, 5 Mar 2024 10:33:39 +0100	[thread overview]
Message-ID: <83c6019f-9c6f-4ad1-87d5-e4f1bdaca93c@leemhuis.info> (raw)
In-Reply-To: <Zd23ZKlNnDKPaU9I@hovoldconsulting.com>

[dropping Linus from CC, we can add him back later when needed]

On 27.02.24 11:20, Johan Hovold wrote:
> On Sun, Feb 25, 2024 at 01:21:46PM +0000, Regzbot (on behalf of Thorsten Leemhuis) wrote:
> 
>> Johan Hovold also deals with multiple issues affecting Lenovo ThinkPad
>> X13s, but he send out patch series to fix some or all of those[1], so
>> with a bit of luck those issues will soon be fixed as well.
>> https://lore.kernel.org/lkml/ZctVmLK4zTwcpW3A@hovoldconsulting.com/

As 6.8 final might be just five days away, could you please help me out
with a short status update wrt. unresolved regressions from your side if
you have a minute? It's easy to get lost in all those issues. :-/ :-D

>> [1]
>> https://lore.kernel.org/lkml/20240217150228.5788-1-johan+linaro@kernel.org/
> 
> This series addresses a use-after-free in the PMIC glink driver caused
> by DRM bridge changes in rc1 and which can result in the internal
> display not showing up on boot.
> 
> The DRM/SoC fixes here have now been merged to drm-misc for 6.8.

What about the others from that series? Can they wait till 6.9? Or are
they on track for 6.8?

> [...]

> But also with these fixes, there are still a couple of regressions
> related to the Qualcomm DRM runtime PM rework in 6.8-rc1. I'll send
> separate reports to track those.

Any decision yet if they are going to be reverted for now?

Am I right assuming those would fix
https://lore.kernel.org/lkml/Zd3kvD02Qvsh2Sid@hovoldconsulting.com/
which did not get even a single reply?

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
If I did something stupid, please tell me, as explained on that page.

  parent reply	other threads:[~2024-03-05  9:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 13:21 Linux regressions report for mainline [2024-02-25] Regzbot (on behalf of Thorsten Leemhuis)
2024-02-25 14:21 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-26 17:33   ` Linus Torvalds
2024-02-27 11:56     ` Thorsten Leemhuis
2024-02-27 10:20 ` Johan Hovold
2024-02-27 12:08   ` Linux regression tracking (Thorsten Leemhuis)
2024-03-05  9:33   ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-03-05 13:51     ` Lenovo ThinkPad X13s regerssions (was Re: Linux regressions report for mainline [2024-02-25]) Johan Hovold
2024-03-05 14:50       ` Linux regression tracking (Thorsten Leemhuis)
2024-03-05 15:08         ` Johan Hovold
2024-03-06  4:19       ` Bjorn Andersson
2024-03-08 12:55         ` Johan Hovold

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=83c6019f-9c6f-4ad1-87d5-e4f1bdaca93c@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.