From: "Linux regression tracking #adding (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linus Walleij <linus.walleij@linaro.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: javierm@redhat.com, mairacanal@riseup.net,
dri-devel@lists.freedesktop.org, jose.exposito89@gmail.com,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH v3 11/13] drm/fb-helper: Fix single-probe color-format selection
Date: Sun, 14 May 2023 14:10:43 +0200 [thread overview]
Message-ID: <ce0b54a6-807c-4afc-279e-022fc9ecaa7e@leemhuis.info> (raw)
In-Reply-To: <CACRpkdZAqnWcq+fzAY0HjHN5=nDHMqb7g9mZNtLM9x4y40vvAw@mail.gmail.com>
[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
On 12.05.23 15:20, Linus Walleij wrote:
> Sorry for late regression detection but this patch regresses
> the Integrator AB IMPD-1 graphics, I bisected down to this
> patch.
>
> On Mon, Jan 2, 2023 at 12:30 PM Thomas Zimmermann <tzimmermann@suse.de> wrote:
> [...]
> Before this patch:
>
> [drm] Initialized pl111 1.0.0 20170317 for c1000000.display on minor 0
> drm-clcd-pl111 c1000000.display: [drm] requested bpp 16, scaled depth down to 15
> drm-clcd-pl111 c1000000.display: enable IM-PD1 CLCD connectors
> Console: switching to colour frame buffer device 80x30
> drm-clcd-pl111 c1000000.display: [drm] fb0: pl111drmfb frame buffer device
>
> After this patch:
>
> [drm] Initialized pl111 1.0.0 20170317 for c1000000.display on minor 0
> drm-clcd-pl111 c1000000.display: [drm] bpp/depth value of 16/16 not supported
> drm-clcd-pl111 c1000000.display: [drm] No compatible format found
> drm-clcd-pl111 c1000000.display: [drm] *ERROR* fbdev: Failed to setup
> generic emulation (ret=-12)
>
> It seems the bpp downscaling stopped to work? [...]
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:
#regzbot ^introduced 37c90d589dc
#regzbot title drm/fb-helper: downscaling apparently stopped to work
with pl110_impd1
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.
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-05-14 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230102112927.26565-1-tzimmermann@suse.de>
[not found] ` <20230102112927.26565-2-tzimmermann@suse.de>
[not found] ` <4Psm6B6Lqkz1QXM@panix3.panix.com>
2023-04-08 11:26 ` [PATCH v3 01/13] firmware/sysfb: Fix EFI/VESA format selection Linux regression tracking #adding (Thorsten Leemhuis)
2023-04-16 12:06 ` Linux regression tracking #update (Thorsten Leemhuis)
[not found] ` <20230102112927.26565-12-tzimmermann@suse.de>
[not found] ` <CACRpkdZAqnWcq+fzAY0HjHN5=nDHMqb7g9mZNtLM9x4y40vvAw@mail.gmail.com>
2023-05-14 12:10 ` Linux regression tracking #adding (Thorsten Leemhuis) [this message]
2023-05-26 12:22 ` [PATCH v3 11/13] drm/fb-helper: Fix single-probe color-format selection Linux regression tracking #update (Thorsten Leemhuis)
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=ce0b54a6-807c-4afc-279e-022fc9ecaa7e@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jose.exposito89@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=mairacanal@riseup.net \
--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;
as well as URLs for NNTP newsgroup(s).