From: Cyril Brulebois <cyril@debamax.com>
To: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: Michal Suchanek <msuchanek@suse.de>,
linux-kernel@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Updating hardcoded "of-display" devices
Date: Wed, 12 Apr 2023 11:55:07 +0200 [thread overview]
Message-ID: <20230412095509.2196162-1-cyril@debamax.com> (raw)
Hi,
We've spotted a regression with the Debian Installer on ppc64el, and
I've confirmed that the first patch fixes fbdev/offb as expected (or at
least works around the regression, see last part of the commit message):
- [PATCH 1/2] fbdev/offb: Update expected device name
Since I've spotted that drm/ofdrm is affected as well, I'm submitting a
similar patch for it, but I can't really test it. I suppose Thomas who
introduced this new driver during the v6.2 release cycle will be able
to take it from there if needed:
- [PATCH 2/2] drm/ofdrm: Update expected device name
Cheers,
--
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
next reply other threads:[~2023-04-13 8:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 9:55 Cyril Brulebois [this message]
2023-04-12 9:55 ` [PATCH 1/2] fbdev/offb: Update expected device name Cyril Brulebois
2023-04-16 12:34 ` Salvatore Bonaccorso
2023-06-15 13:03 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-15 13:06 ` Thomas Zimmermann
2023-06-15 13:21 ` Michal Suchánek
2023-06-15 20:09 ` Rob Herring
2023-06-15 21:19 ` Cyril Brulebois
2023-06-20 6:24 ` Helge Deller
2023-06-20 8:04 ` Michal Suchánek
2023-06-15 13:12 ` Cyril Brulebois
2023-04-22 9:50 ` Helge Deller
2023-04-24 7:31 ` Geert Uytterhoeven
2023-07-10 16:36 ` Michal Suchánek
2023-04-12 9:55 ` [PATCH 2/2] drm/ofdrm: " Cyril Brulebois
2023-04-24 7:33 ` Geert Uytterhoeven
2023-04-24 9:07 ` Thomas Zimmermann
2023-04-24 9:35 ` Helge Deller
2023-05-22 9:37 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:44 ` Michal Suchánek
2023-07-10 16:36 ` Michal Suchánek
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=20230412095509.2196162-1-cyril@debamax.com \
--to=cyril@debamax.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msuchanek@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).