All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203325] 5.1 amdgpu on polaris11: broken text-fb multihead, works in X
Date: Fri, 19 Apr 2019 05:06:43 +0000	[thread overview]
Message-ID: <bug-203325-2300-3rI1JBL0aX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203325-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=203325

Duncan (1i5t5.duncan@cox.net) changed:

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

--- Comment #5 from Duncan (1i5t5.duncan@cox.net) ---
(In reply to Alex Deucher from comment #4)
> Should be fixed with this patch:
> https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-5.
> 1&id=c238bfe0be9ef7420f7669a69e27c8c8f4d8a568

Thanks.  That's in mainline now, merged just today, and does indeed appear to
fix it. =:^)

I'm confused between code_fix and patch_already_available, and the status-help
link doesn't help because those are apparently kernel-bugzilla-specific and the
documentation isn't so doesn't cover them (bug filed on that years ago,
but...), so I'll guess code_fix.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2019-04-19  5:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15  9:50 [Bug 203325] New: 5.1 amdgpu on polaris11: broken text-fb multihead, works in X bugzilla-daemon
2019-04-15  9:54 ` [Bug 203325] " bugzilla-daemon
2019-04-15  9:56 ` bugzilla-daemon
2019-04-15 10:06 ` bugzilla-daemon
2019-04-15 14:15 ` bugzilla-daemon
2019-04-19  5:06 ` 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-203325-2300-3rI1JBL0aX@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.