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 110956] List of 19.20-812932 release mistakes
Date: Sat, 22 Jun 2019 16:11:16 +0000	[thread overview]
Message-ID: <bug-110956-502-T5bx1ssuI8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110956-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Eric Engestrom <fdo-bugs@engestrom.ch> ---
OK, there are 4 issues left:

110965 & 110964 are about the docs on https://amdgpu-install.readthedocs.io/; a
quick look at the repo shows only one member, Tim Writer
(https://gitlab.com/amdgpu/docs/amdgpu-install/-/project_members).
You should try to contact him about these, or maybe simply send him an MR with
your updates.
I'll close these two now.

110958 is about the docs on the AMD.com website, which we have no control over,
but there are some AMD devs that read the bug tracker; maybe they'll see this
bug and know how to update the docs.

Lastly, 110966 is about the Vulkan SDK from LunarG; I don't know much about it
other than the fact it is used on Windows to distribute the vulkan loader (the
thing that manages the various vendors' vulkan drivers).
As for the api version numbers, 1.1.x should be all compatible with one
another, aside from missing features from newer releases, obviously.

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

[-- Attachment #1.2: Type: text/html, Size: 2019 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-06-22 16:11 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 19:41 [Bug 110956] List of 19.20-812932 release mistakes bugzilla-daemon
2019-06-21 23:19 ` bugzilla-daemon
2019-06-22  4:53 ` bugzilla-daemon
2019-06-22 15:41 ` bugzilla-daemon
2019-06-22 15:42 ` bugzilla-daemon
2019-06-22 15:45 ` bugzilla-daemon
2019-06-22 15:46 ` bugzilla-daemon
2019-06-22 15:48 ` bugzilla-daemon
2019-06-22 15:49 ` bugzilla-daemon
2019-06-22 15:49 ` bugzilla-daemon
2019-06-22 15:52 ` bugzilla-daemon
2019-06-22 15:54 ` bugzilla-daemon
2019-06-22 16:11 ` bugzilla-daemon [this message]
2019-06-22 16:13 ` bugzilla-daemon
2019-06-22 16:13 ` bugzilla-daemon
2019-06-22 16:37 ` bugzilla-daemon
2019-06-22 16:48 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-06-24  8:59 ` bugzilla-daemon
2019-07-29 20:05 ` bugzilla-daemon
2019-07-29 20:08 ` bugzilla-daemon
2019-07-29 20:15 ` bugzilla-daemon
2019-07-29 20:24 ` bugzilla-daemon
2019-07-29 20:28 ` bugzilla-daemon
2019-07-31 15:24 ` bugzilla-daemon
2019-11-19  8:00 ` bugzilla-daemon
2019-11-19  8:00 ` bugzilla-daemon
2019-11-19  8:00 ` bugzilla-daemon
2019-11-19  8:00 ` bugzilla-daemon
2019-11-19  8:00 ` bugzilla-daemon
2019-11-19  8:00 ` bugzilla-daemon
2019-11-19  8:00 ` bugzilla-daemon
2019-11-19  8:00 ` 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-110956-502-T5bx1ssuI8@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