dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107049] monitor not found in 4.17+ kernel
Date: Mon, 06 May 2019 08:52:13 +0000	[thread overview]
Message-ID: <bug-107049-502-Eq7fXmL11H@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107049-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 703 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107049

Michel Dänzer <michel@daenzer.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #11 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Dan Horák from comment #10)
> and the dc=0 was still required for 5.0, so sound like an improvement in 5.1

Glad to hear it's fixed in 5.1! Thanks for the follow-ups, resolving
accordingly.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2019-05-06  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 10:16 [Bug 107049] monitor not found in 4.17+ kernel bugzilla-daemon
2018-06-27 10:17 ` bugzilla-daemon
2018-06-27 10:19 ` bugzilla-daemon
2018-06-27 10:24 ` bugzilla-daemon
2018-06-27 10:51 ` bugzilla-daemon
2018-06-27 11:14 ` bugzilla-daemon
2018-06-27 14:33 ` bugzilla-daemon
2018-06-27 14:44 ` bugzilla-daemon
2018-06-27 14:46 ` bugzilla-daemon
2019-05-02  6:18 ` bugzilla-daemon
2019-05-04 13:04 ` bugzilla-daemon
2019-05-06  8:52 ` bugzilla-daemon [this message]

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=bug-107049-502-Eq7fXmL11H@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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