From: Rafael Passos <rafael@rcpassos.me>
To: linux-doc@vger.kernel.org
Cc: corbet@lwn.net, skhan@linuxfoundation.org
Subject: [PATCH 2/3] Documentation: xe_drm: fix chars used for subsection
Date: Sat, 20 Jun 2026 17:16:34 -0300 [thread overview]
Message-ID: <20260620201732.94141-3-rafael@rcpassos.me> (raw)
In-Reply-To: <20260620201732.94141-1-rafael@rcpassos.me>
Equal signs are reserved for document tiles"="
this file docs gets imported by driver-uapi.rst,
and the page title is defined there.
Signed-off-by: Rafael Passos <rafael@rcpassos.me>
---
include/uapi/drm/xe_drm.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
index 48e9f1fdb78d..4dfb30e6c8a8 100644
--- a/include/uapi/drm/xe_drm.h
+++ b/include/uapi/drm/xe_drm.h
@@ -2537,21 +2537,21 @@ struct drm_xe_exec_queue_set_property {
* Refer to Documentation/netlink/specs/drm_ras.yaml for complete interface specification.
*
* Node Registration
- * =================
+ * -----------------
*
* The driver registers DRM RAS nodes for each error severity level.
* enum drm_xe_ras_error_severity defines the node-id, while DRM_XE_RAS_ERROR_SEVERITY_NAMES maps
* node-id to node-name.
*
* Error Classification
- * ====================
+ * --------------------
*
* Each node contains a list of error counters. Each error is identified by a error-id and
* an error-name. enum drm_xe_ras_error_component defines the error-id, while
* DRM_XE_RAS_ERROR_COMPONENT_NAMES maps error-id to error-name.
*
* User Interface
- * ==============
+ * --------------
*
* To retrieve error values of a error counter, userspace applications should
* follow the below steps:
--
2.53.0
next prev parent reply other threads:[~2026-06-20 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 20:16 [PATCH 0/3] Documentation: fix doc build errors for 7.2 Rafael Passos
2026-06-20 20:16 ` [PATCH 1/3] Documentation: iio: fix Malformed table for ltc4283 Rafael Passos
2026-06-20 21:29 ` Randy Dunlap
2026-06-20 20:16 ` Rafael Passos [this message]
2026-06-20 21:42 ` [PATCH 2/3] Documentation: xe_drm: fix chars used for subsection Randy Dunlap
2026-06-21 2:38 ` Rafael Passos
2026-06-21 3:43 ` Randy Dunlap
2026-06-20 20:16 ` [PATCH 3/3] Documentation: ABI: fix description field indentation Rafael Passos
2026-06-20 21:33 ` Randy Dunlap
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=20260620201732.94141-3-rafael@rcpassos.me \
--to=rafael@rcpassos.me \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=skhan@linuxfoundation.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