From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103404] HDMI Audio with RX Vega not working on drm-next-4.15-dc (device listed as unconnected)
Date: Tue, 31 Oct 2017 21:08:53 +0000 [thread overview]
Message-ID: <bug-103404-502-vsPDMCdgCd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103404-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103404
--- Comment #10 from randomsalad@gmail.com ---
Created attachment 135197
--> https://bugs.freedesktop.org/attachment.cgi?id=135197&action=edit
Compilation error for the patch
The proposed patch doesn't compile when applied to an otherwise clean version
of drm-next-4.15-dc (commit id 9b38bd1b8f5c874c3d1f330e0dcf4e7d84137477 at time
of writing). Does it rely on other changes present on the WIP branch? I've
attached the compilation errors.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1582 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-10-31 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 15:07 [Bug 103404] HDMI Audio with RX Vega not working on drm-next-4.15-dc (device listed as unconnected) bugzilla-daemon
2017-10-22 15:09 ` bugzilla-daemon
2017-10-22 15:10 ` bugzilla-daemon
2017-10-22 15:11 ` bugzilla-daemon
2017-10-29 10:31 ` bugzilla-daemon
2017-10-30 14:12 ` bugzilla-daemon
2017-10-31 13:46 ` bugzilla-daemon
2017-10-31 20:33 ` bugzilla-daemon
2017-10-31 20:34 ` bugzilla-daemon
2017-10-31 20:36 ` bugzilla-daemon
2017-10-31 21:08 ` bugzilla-daemon [this message]
2017-10-31 21:12 ` bugzilla-daemon
2017-10-31 21:21 ` bugzilla-daemon
2017-11-01 14:03 ` bugzilla-daemon
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-103404-502-vsPDMCdgCd@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 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.