From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105632] X won't start at "drm/amd/pp: Simplified the avfs btc state on smu7"
Date: Tue, 20 Mar 2018 19:39:53 +0000 [thread overview]
Message-ID: <bug-105632-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1042 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105632
Bug ID: 105632
Summary: X won't start at "drm/amd/pp: Simplified the avfs btc
state on smu7"
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: bug0xa3d2@hushmail.com
X won't start at "drm/amd/pp: Simplified the avfs btc state on smu7" on
"drm-next-4.17".
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.17&id=116af45059139e8a156c9993bc4aa94625bd9c5e
Odd, I thought I remember X starting with commit, "amdgpu/dm: Default PRE_VEGA
ASIC support to 'y'" on the the "drm-next-4.17-wip" branch and that commit is
AFTER "drm/amd/pp: Simplified the avfs btc state on smu7" on branch
"drm-next-4.17".
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2549 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 reply other threads:[~2018-03-20 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 19:39 bugzilla-daemon [this message]
2018-03-20 20:50 ` [Bug 105632] X won't start at "drm/amd/pp: Simplified the avfs btc state on smu7" bugzilla-daemon
2018-03-20 22:51 ` 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-105632-502@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.