linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dirk Gouders <dirk@gouders.net>
To: Lyude Paul <lyude@redhat.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
	"Wayne Lin" <Wayne.Lin@amd.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
	"Jani Nikula" <jani.nikula@intel.com>,
	"Imre Deak" <imre.deak@intel.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Sean Paul" <sean@poorly.run>
Subject: Regression bisected: drm/display/dp_mst: Move all payload info into the atomic state
Date: Thu, 10 Nov 2022 23:32:05 +0100	[thread overview]
Message-ID: <ghwn827862.fsf@gouders.net> (raw)

Hello,

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.

Dirk

             reply	other threads:[~2022-11-10 22:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 22:32 Dirk Gouders [this message]
2022-11-11 20:50 ` Regression bisected: drm/display/dp_mst: Move all payload info into the atomic state Lyude Paul
2022-11-11 22:00   ` Dirk Gouders
2022-11-13  9:28 ` Regression bisected: drm/display/dp_mst: Move all payload info into the atomic state #forregzbot Thorsten Leemhuis
2022-11-20 17:29   ` Thorsten Leemhuis
2022-11-23 15:43   ` Thorsten Leemhuis
2023-01-13 20:38     ` Salvatore Bonaccorso

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=ghwn827862.fsf@gouders.net \
    --to=dirk@gouders.net \
    --cc=Jerry.Zuo@amd.com \
    --cc=Wayne.Lin@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=imre.deak@intel.com \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.com \
    --cc=sean@poorly.run \
    --cc=ville.syrjala@linux.intel.com \
    /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).