From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110866] Revert 8059add0478e29cb641936011a8fcc9ce9fd80be for stable 5.1.x
Date: Sun, 09 Jun 2019 13:29:38 +0000 [thread overview]
Message-ID: <bug-110866-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1223 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110866
Bug ID: 110866
Summary: Revert 8059add0478e29cb641936011a8fcc9ce9fd80be for
stable 5.1.x
Product: DRI
Version: unspecified
Hardware: Other
URL: https://bugzilla.kernel.org/show_bug.cgi?id=203679
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: nrndda@gmail.com
Kernel 5.0 marked as EOL and 5.1 is broken for RADV VR on Steam.
Copy of description from kernel bugzilla:
Original commit 8059add0478e29cb641936011a8fcc9ce9fd80be
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/drm_ioctl.c?id=8059add0478e29cb641936011a8fcc9ce9fd80be)
was added in 5.1 merge cycle and reverted by
dbb92471674a48892f5e50779425e03388073ab9
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbb92471674a48892f5e50779425e03388073ab9)
in 5.2. So radv is still broken in 5.1.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2873 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
next reply other threads:[~2019-06-09 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 13:29 bugzilla-daemon [this message]
2019-06-11 8:59 ` [Bug 110866] Revert 8059add0478e29cb641936011a8fcc9ce9fd80be for stable 5.1.x bugzilla-daemon
2019-06-15 14:43 ` 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-110866-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox