From: "Pierre Asselin" <pa@panix.com>
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Pierre Asselin" <pa@panix.com>,
dri-devel@lists.freedesktop.org,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Javier Martinez Canillas" <javierm@redhat.com>,
linux-kernel@vger.kernel.org,
"Hans de Goede" <hdegoede@redhat.com>,
"Ard Biesheuvel" <ardb@kernel.org>
Subject: Re: [PATCH v3] firmware/sysfb: Fix VESA format selection
Date: Fri, 21 Apr 2023 09:42:25 -0400 [thread overview]
Message-ID: <40075ac685423d46663dd6a4038add90.squirrel@mail.panix.com> (raw)
In-Reply-To: <d8d22c77-1bde-774f-aa6e-41234ffa6e8d@suse.de>
Thomas Zimmerman writes:
>
> Am 21.04.23 um 13:32 schrieb Linux regression tracking (Thorsten
> Leemhuis):
>>
>> Pierre, Tomas, Javier, et. al: how many "legacy BIOSes" do we suspect
>> are affected by this?
So far, two:
1) my Gateway laptop (Intel(R) Core(TM) Duo CPU,
Phoenix BIOS 83.08 Revision: 131.8 Release Date: 03/06/07)
2) my Dell Precision T3610 (Intel(R) Xeon(R) CPU E5-1650,
Dell BIOS A19 Revision: 65.19 Release Date: 09/11/2019)
I don't know how to give a more precise description.
>> might it be worth asking Linus to merge this patch directly[1]?
>
> IMHO it's a fairly obscure bug and certainly not a release blocker. I'll
> send it through the regular channels of the DRM subsystem.
I agree. Even when the regression bites, it's not a blocker. The screen
is strange but readable.
--PA
next prev parent reply other threads:[~2023-04-21 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 15:57 Pierre Asselin
2023-04-20 16:05 ` Pierre Asselin
2023-04-21 11:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-21 11:35 ` Thomas Zimmermann
2023-04-21 13:42 ` Pierre Asselin [this message]
2023-04-21 12:37 ` Thomas Zimmermann
2023-05-10 17:25 ` Pierre Asselin
2023-05-11 8:05 ` Thomas Zimmermann
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=40075ac685423d46663dd6a4038add90.squirrel@mail.panix.com \
--to=pa@panix.com \
--cc=ardb@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®