summaryrefslogtreecommitdiff
path: root/dev-util/lttng-modules/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@koprulu.sector>2022-11-05 09:17:35 +0000
committerV3n3RiX <venerix@koprulu.sector>2022-11-05 09:17:35 +0000
commit54c42eb42df420f52e032fcba7727c326ef01094 (patch)
tree0dee719f67aa7ad3bfb64c3a46912acad885d738 /dev-util/lttng-modules/metadata.xml
parenta8b01fd62375e0df65d5f8f20c5ee142ec6739b6 (diff)
gentoo auto-resync : 05:11:2022 - 09:17:35
Diffstat (limited to 'dev-util/lttng-modules/metadata.xml')
-rw-r--r--dev-util/lttng-modules/metadata.xml3
1 files changed, 3 insertions, 0 deletions
diff --git a/dev-util/lttng-modules/metadata.xml b/dev-util/lttng-modules/metadata.xml
index a559bf3a7dcd..a3465ae4f01d 100644
--- a/dev-util/lttng-modules/metadata.xml
+++ b/dev-util/lttng-modules/metadata.xml
@@ -5,4 +5,7 @@
<longdescription>
Use the kernel tracer if you are debugging a system-wide performance problem or a kernel problem. This tracer comes with an instrumentation patch for most kernel subsystems, which is enough to debug many problems. This includes system calls, IRQs, traps, memory management, softIRQs, scheduling and many others. Of course, the kernel tracer allows you to add your own instrumentation anywhere in the kernel code.
</longdescription>
+ <upstream>
+ <remote-id type="github">lttng/lttng-modules</remote-id>
+ </upstream>
</pkgmetadata>