From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102491] OpenCL image processing produces artifacts on Cape Verde 7770
Date: Tue, 19 Nov 2019 07:58:32 +0000 [thread overview]
Message-ID: <bug-102491-502-PRZLWZaNA1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102491-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102491
Martin Peres <martin.peres@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|NEW |RESOLVED
--- Comment #6 from Martin Peres <martin.peres@free.fr> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/13.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2405 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
prev parent reply other threads:[~2019-11-19 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 8:33 [Bug 102491] OpenCL app gets CL_OUT_OF_HOST_MEMORY on Cape Verde 7770 bugzilla-daemon
2017-08-31 8:34 ` bugzilla-daemon
2017-08-31 8:34 ` bugzilla-daemon
2017-08-31 8:35 ` bugzilla-daemon
2017-08-31 8:37 ` bugzilla-daemon
2017-12-28 13:08 ` bugzilla-daemon
2017-12-28 13:09 ` [Bug 102491] OpenCL image processing produces artifacts " bugzilla-daemon
2019-11-19 7:58 ` 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-102491-502-PRZLWZaNA1@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