public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tom Rix <Tom.Rix@amd.com>
To: git-commits@fedoraproject.org
Subject: [rpms/rocm] epel10: Add rocm-rdc
Date: Mon, 15 Jun 2026 13:48:57 GMT [thread overview]
Message-ID: <178153133771.1.13320606118653374076.rpms-rocm-e8a755b7a8c3@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/rocm
Branch : epel10
Commit : e8a755b7a8c3c1ed08d15f8c2148a3b90a9a6b09
Author : Tom Rix <Tom.Rix@amd.com>
Date : 2026-04-08T11:33:40-07:00
Stats : +6/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/rocm/c/e8a755b7a8c3c1ed08d15f8c2148a3b90a9a6b09?branch=epel10
Log:
Add rocm-rdc
Signed-off-by: Tom Rix <Tom.Rix@amd.com>
---
diff --git a/rocm.spec b/rocm.spec
index a39ccb1..2d33a2b 100644
--- a/rocm.spec
+++ b/rocm.spec
@@ -25,7 +25,7 @@
Name: rocm
Version: %{rocm_version}
-Release: 2%{?dist}
+Release: 3%{?dist}
Summary: ROCm tools for computing on AMD GPU
License: MIT
@@ -70,6 +70,7 @@ Requires: rocm-core >= %{rocm_release}
Requires: rocm-omp >= %{rocm_release}
Requires: rocm-opencl >= %{rocm_release}
Requires: rocm-origami
+Requires: rocm-rdc >= %{rocm_release}
Requires: rocm-rpp >= %{rocm_release}
Requires: rocprofiler-register >= %{rocm_release}
Requires: roctracer >= %{rocm_release}
@@ -132,6 +133,7 @@ Requires: rocjpeg-devel >= %{rocm_release}
Requires: rocm-core-devel >= %{rocm_release}
Requires: rocm-examples >= %{rocm_release}
Requires: rocm-omp-static >= %{rocm_release}
+Requires: rocm-rdc-devel >= %{rocm_release}
Requires: rocm-rpp-devel >= %{rocm_release}
Requires: rocprofiler-register-devel >= %{rocm_release}
Requires: rocthrust-devel >= %{rocm_release}
@@ -184,6 +186,9 @@ install -pm 644 %{SOURCE0} .
%license License.txt
%changelog
+* Wed Apr 8 2026 Tom Rix <Tom.Rix@amd.com> - 7.2.0-3
+- Add rocm-rdc
+
* Thu Mar 19 2026 Tom Rix <Tom.Rix@amd.com> - 7.2.0-2
- Remove tensile from rocm-devel
reply other threads:[~2026-06-15 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178153133771.1.13320606118653374076.rpms-rocm-e8a755b7a8c3@fedoraproject.org \
--to=tom.rix@amd.com \
--cc=git-commits@fedoraproject.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