From: Slade Watkins <srw@sladewatkins.net>
To: Jerry Ling <jiling@cern.ch>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Regression on 5.19.12, display flickering on Framework laptop
Date: Fri, 30 Sep 2022 08:49:41 -0400 [thread overview]
Message-ID: <3A2E2B7D-801C-461E-84DB-FFFB08DC7241@sladewatkins.net> (raw)
In-Reply-To: <aa8b9724-50c6-ae2e-062d-3791144ac97e@cern.ch>
> On Sep 30, 2022, at 8:26 AM, Jerry Ling <jiling@cern.ch> wrote:
>
> Hi,
>
> looks like someone has done it: https://bbs.archlinux.org/viewtopic.php?pid=2059823#p2059823
>
> and the bisect points to:
>
> |# first bad commit: [fc6aff984b1c63d6b9e54f5eff9cc5ac5840bc8c] drm/i915/bios: Split VBT data into per-panel vs. global parts Best, Jerry |
I just got Thorsten’s email about this [1]. Alright then.
[1] https://lore.kernel.org/all/b85bc2cf-5ea5-c5fb-465c-cd6637f6d30f@leemhuis.info/
-srw
next prev parent reply other threads:[~2022-09-30 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 2:26 Regression on 5.19.12, display flickering on Framework laptop Jerry Ling
2022-09-30 4:37 ` Greg KH
2022-09-30 5:59 ` Greg KH
2022-09-30 11:11 ` Slade Watkins
2022-09-30 11:22 ` Greg Kroah-Hartman
2022-09-30 11:56 ` Slade Watkins
2022-09-30 12:26 ` Jerry Ling
2022-09-30 12:49 ` Slade Watkins [this message]
2022-10-01 10:07 ` Thorsten Leemhuis
2022-10-01 12:34 ` Hans de Goede
2022-10-03 17:45 ` Ville Syrjälä
2022-10-03 17:48 ` Ville Syrjälä
2022-10-03 18:28 ` Thorsten Leemhuis
2022-10-04 12:35 ` Ville Syrjälä
2022-10-04 12:57 ` Greg Kroah-Hartman
[not found] ` <9aae6b15-265a-4ef9-87c1-83dfe5094378@smtp-relay.sendinblue.com>
2022-10-04 13:40 ` Greg Kroah-Hartman
2022-10-04 13:44 ` Ville Syrjälä
2022-10-04 14:28 ` Greg Kroah-Hartman
2022-09-30 5:10 ` Thorsten Leemhuis
2022-09-30 13:05 ` Jerry Ling
2022-09-30 15:02 ` Greg KH
2022-10-03 16:42 ` David Matthew Mattli
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=3A2E2B7D-801C-461E-84DB-FFFB08DC7241@sladewatkins.net \
--to=srw@sladewatkins.net \
--cc=gregkh@linuxfoundation.org \
--cc=jiling@cern.ch \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.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).