From: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH] drm/xe: Fix kernel doc warning for PMU events
Date: Tue, 19 Sep 2023 12:06:11 +0530 [thread overview]
Message-ID: <20230919063611.14236-1-aravind.iddamsetty@linux.intel.com> (raw)
Add DOC keyword to PMU events comment in include/drm/xe_drm.h to make it
kernel doc format.
Fixes: 4a9681392cec ("drm/xe/pmu: Enable PMU interface")
Signed-off-by: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
---
include/uapi/drm/xe_drm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
index 63863eda8355..6ab85c7fed36 100644
--- a/include/uapi/drm/xe_drm.h
+++ b/include/uapi/drm/xe_drm.h
@@ -1054,7 +1054,7 @@ struct drm_xe_vm_madvise {
};
/**
- * XE PMU event config IDs
+ * DOC: XE PMU event config IDs
*
* Check 'man perf_event_open' to use these ID's in 'struct perf_event_attr'
* as part of perf_event_open syscall to read a particular event.
--
2.25.1
next reply other threads:[~2023-09-19 6:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 6:36 Aravind Iddamsetty [this message]
2023-09-19 6:29 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Fix kernel doc warning for PMU events Patchwork
2023-09-19 6:29 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-19 6:30 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-19 6:37 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-19 6:38 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-19 6:39 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-19 6:47 ` [Intel-xe] [PATCH] " Dixit, Ashutosh
2023-09-19 7:07 ` Aravind Iddamsetty
2023-09-19 7:10 ` [Intel-xe] ✓ CI.BAT: success for " Patchwork
2023-09-19 7:46 ` [Intel-xe] [PATCH] " Thomas Hellström
2023-09-19 7:59 ` Aravind Iddamsetty
2023-09-19 13:27 ` Gustavo Sousa
2023-09-20 8:26 ` Aravind Iddamsetty
2023-09-20 13:21 ` Gustavo Sousa
2023-09-21 5:43 ` Aravind Iddamsetty
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=20230919063611.14236-1-aravind.iddamsetty@linux.intel.com \
--to=aravind.iddamsetty@linux.intel.com \
--cc=intel-xe@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