Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Sender: Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Date:   Fri, 13 Jan 2023 21:38:50 +0100
From:   Salvatore Bonaccorso <carnil@debian.org>
To:     Thorsten Leemhuis <regressions@leemhuis.info>
Cc:     "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
        Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Regression bisected: drm/display/dp_mst: Move all payload info
 into the atomic state #forregzbot
Message-ID: <Y8HBWgieidOo4S1c@eldamar.lan>
References: <ghwn827862.fsf@gouders.net>
 <45ca4839-fa2a-9511-fd47-2d75fa3766cd@leemhuis.info>
 <038cecb9-aab2-bcd7-f003-46ca637942d8@leemhuis.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <038cecb9-aab2-bcd7-f003-46ca637942d8@leemhuis.info>
Precedence: bulk

hi Thorsten,

On Wed, Nov 23, 2022 at 04:43:41PM +0100, Thorsten Leemhuis wrote:
> [Note: this mail is primarily send for documentation purposes and/or for
> regzbot, my Linux kernel regression tracking bot. That's why I removed
> most or all folks from the list of recipients, but left any that looked
> like a mailing lists. These mails usually contain '#forregzbot' in the
> subject, to make them easy to spot and filter out.]
> 
> On 13.11.22 10:28, Thorsten Leemhuis wrote:
> > On 10.11.22 23:32, Dirk Gouders wrote:
> >>
> >> I noticed a regression with Linus' current tree and bisected it to
> >> 4d07b0bc403403 (drm/display/dp_mst: Move all payload info into the atomic state):
> >>
> >> I have two monitors connected to my laptop's USB-C port and since this
> >> patch, one of the monitors remains dark.
> >>
> >> Please let me know if I can provide additional information that could help
> >> to investigate this problem.
> > 
> > Thanks for the report. To be sure below issue doesn't fall through the
> > cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
> > tracking bot:
> > 
> > #regzbot introduced 4d07b0bc403403 ^
> > https://gitlab.freedesktop.org/drm/amd/-/issues/2171
> > #regzbot title drm: amdgpu: No payload for [MST PORT:0000000006da5d29]
> > found in mst state 00000000b0e556d6" on system resume with TBT dock
> > connected.
> > #regzbot ignore-activity
> 
> #regzbot fixed-by: d60b82aa

I have a question on this regression tracking, as I noticed the
https://gitlab.freedesktop.org/drm/amd/-/issues/2171 issue which is
still open, does not appear on
https://linux-regtracking.leemhuis.info/regzbot/mainline/ :

Is the fixed-by marking above correct? There is still ongoing
discussion and Mario Limoncello is proposing to revert commit
4d07b0bc403403438d9cf88450506240c5faf92f . Cf.
https://gitlab.freedesktop.org/drm/amd/-/issues/2171#note_1722420 and
https://patchwork.freedesktop.org/patch/518080/ .

So is it needed to to unmark it as fixed or do I miss something here?

Regards,
Salvatore