From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/opencl/
Date: Mon, 21 Oct 2024 22:48:14 +0000 (UTC) [thread overview]
Message-ID: <1729550871.1e538516e220385452a6e7904aee2a1abeeab30d.mattst88@gentoo> (raw)
commit: 1e538516e220385452a6e7904aee2a1abeeab30d
Author: Tomas Fabrizio Orsi <torsi <AT> fi <DOT> uba <DOT> ar>
AuthorDate: Sat Oct 12 14:33:31 2024 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Mon Oct 21 22:47:51 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1e538516
virtual/opencl: Remove missing uvm from nvidia-drivers message
Closes: https://bugs.gentoo.org/941391
Closes: https://github.com/gentoo/gentoo/pull/38952
Signed-off-by: Tomas Fabrizio Orsi <torsi <AT> fi.uba.ar>
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
virtual/opencl/opencl-3-r3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virtual/opencl/opencl-3-r3.ebuild b/virtual/opencl/opencl-3-r3.ebuild
index 6d4f304d5372..5e9e92b8619a 100644
--- a/virtual/opencl/opencl-3-r3.ebuild
+++ b/virtual/opencl/opencl-3-r3.ebuild
@@ -27,7 +27,7 @@ pkg_postinst() {
elog " * proprietary:"
elog " - dev-libs/amdgpu-pro-opencl - AMD Polaris GPUs. 32-bit support;"
elog " - dev-util/intel-ocl-sdk - Intel CPUs (*not* GPUs). 64-bit only;"
- elog " - x11-drivers/nvidia-drivers[uvm] - Nvidia GPUs; specific package versions"
+ elog " - x11-drivers/nvidia-drivers - Nvidia GPUs; specific package versions"
elog " required for older devices [2]. 32-bit support."
elog
elog " [1] https://dri.freedesktop.org/wiki/GalliumCompute/"
next reply other threads:[~2024-10-21 22:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 22:48 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-16 20:50 [gentoo-commits] repo/gentoo:master commit in: virtual/opencl/ Conrad Kostecki
2025-04-10 20:15 Conrad Kostecki
2025-04-06 15:56 Conrad Kostecki
2025-04-06 15:06 Conrad Kostecki
2025-01-15 18:44 Sam James
2025-01-05 1:37 Sam James
2024-05-23 13:34 WANG Xuerui
2023-04-13 3:03 Sam James
2023-04-12 6:05 Yixun Lan
2022-10-04 3:18 Sam James
2022-07-26 4:49 Sam James
2022-07-24 1:07 Sam James
2022-07-24 1:04 Sam James
2021-05-23 12:54 Marek Szuba
2020-08-25 10:39 Marek Szuba
2020-05-18 20:40 Matt Turner
2020-05-14 21:29 Thomas Deutschmann
2020-05-12 12:50 Mikle Kolyada
2020-04-10 13:31 Marek Szuba
2020-04-01 21:15 Marek Szuba
2020-04-01 21:15 Marek Szuba
2020-03-25 13:36 Marek Szuba
2020-03-11 20:19 Matt Turner
2020-02-28 12:08 Marek Szuba
2020-02-28 12:03 Marek Szuba
2020-02-25 9:07 Marek Szuba
2020-02-24 19:11 Marek Szuba
2019-09-21 17:11 Matt Turner
2019-09-20 12:17 Agostino Sarubbo
2019-09-20 12:14 Agostino Sarubbo
2019-08-15 16:27 Craig Andrews
2019-07-10 18:07 Marek Szuba
2019-05-08 19:21 Mikle Kolyada
2019-04-25 22:32 Pacho Ramos
2019-04-19 22:39 Pacho Ramos
2018-07-09 16:51 Michał Górny
2018-05-12 2:45 Matt Turner
2018-05-07 19:22 Thomas Deutschmann
2018-05-06 12:26 Mikle Kolyada
2017-11-24 6:06 Matt Turner
2017-08-09 15:10 Marek Szuba
2017-06-18 16:46 Alexis Ballier
2017-03-25 0:45 Matt Turner
2017-01-26 10:40 Marek Szuba
2017-01-25 1:00 Matt Turner
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=1729550871.1e538516e220385452a6e7904aee2a1abeeab30d.mattst88@gentoo \
--to=mattst88@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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