From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Framebuffer <linux-fbdev@vger.kernel.org>,
DRI Development List <dri-devel@lists.freedesktop.org>,
Linux Nouveau/NVIDIA <nouveau@lists.freedesktop.org>,
Linux Stable <stable@vger.kernel.org>
Cc: Antonino Daplas <adaplas@gmail.com>, Helge Deller <deller@gmx.de>,
Felix Miata <mrmazda@earthlink.net>,
Ben Skeggs <bskeggs@redhat.com>, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [Nouveau] Fwd: absent both plymouth, and video= on linu lines, vtty[1-6] framebuffers produce vast raster right and bottom borders on the larger resolution of two displays
Date: Thu, 25 May 2023 13:24:42 +0200 [thread overview]
Message-ID: <d4879ff1-b9ac-0373-ceb2-beaa645fba23@leemhuis.info> (raw)
In-Reply-To: <585f36f8-431a-e929-0a04-ffb65f02e9df@gmail.com>
On 25.05.23 12:55, Bagas Sanjaya wrote:
> On 5/25/23 17:52, Bagas Sanjaya wrote:
>>
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>> [...]
>> Anyway, I'm adding it to regzbot:
>>
>> #regzbot introduced: v6.1.12..v6.2.12
>> #regzbot title: vast raster right and bottom borders on larger display (two displays with inequal resolution) unless forcing resolution with video= parameter
Bagas, thx again for your efforts, much appreciated. But I guess for drm
drivers that have a line like
B: https://gitlab.freedesktop.org/drm/[...]
in MAINTAINERS (which includes all the popular drm drivers) this just
creates a lot of confusion for everyone, as one issue will likely end up
being discussed in two or three places in parallel (bugzilla,
freedesktop, email). Better tell reporters to move their issue to the
freedesktop drm tracker and close the ticket in bugzilla. And don't get
regzbot involved, as it for now it sadly is unable to monitor the
freedesktop drm tracker (sooner or later I'll fix that, but for now it's
a blind spot :-/).
Pretty sure none of the DRM developers will disagree, but if I'm wrong,
please holler.
> Oops, I forget to add bugzilla link:
>
> #regzbot introduced: v6.1.12..v6.2.12 https://bugzilla.kernel.org/show_bug.cgi?id=217479
> #regzbot from: Felix Miata <mrmazda@earthlink.net>
Side note: that currently does not work with regzbot. :-/ Whatever, I'll
remove it from the tracking due to above reasons:
#regzbot inconclusive: sadly not tracked for now
Ciao, Thorsten
next prev parent reply other threads:[~2023-05-25 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 10:52 Fwd: absent both plymouth, and video= on linu lines, vtty[1-6] framebuffers produce vast raster right and bottom borders on the larger resolution of two displays Bagas Sanjaya
2023-05-25 10:55 ` Bagas Sanjaya
2023-05-25 11:24 ` Thorsten Leemhuis [this message]
2023-05-25 14:05 ` [Nouveau] " Bagas Sanjaya
2023-05-25 11:37 ` Bagas Sanjaya
2023-05-25 14:04 ` Bagas Sanjaya
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=d4879ff1-b9ac-0373-ceb2-beaa645fba23@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=adaplas@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmazda@earthlink.net \
--cc=nouveau@lists.freedesktop.org \
--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).