From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Rafael Passos <rafael@rcpassos.me>
Cc: <matthew.brost@intel.com>, <thomas.hellstrom@linux.intel.com>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, Randy Dunlap <rdunlap@infradead.org>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH RESEND v2] Documentation: xe_drm: fix chars used for subsection
Date: Fri, 3 Jul 2026 14:35:55 -0400 [thread overview]
Message-ID: <akgBC8A9h8nIyEYd@intel.com> (raw)
In-Reply-To: <20260701012141.167868-1-rafael@rcpassos.me>
On Tue, Jun 30, 2026 at 10:20:58PM -0300, Rafael Passos wrote:
> Fixes "ERROR: A level 2 section cannot be used here".
> Equal signs are reserved for document titles.
> This file docs gets imported by driver-uapi.rst,
> and the page title is defined there.
>
>
> Signed-off-by: Rafael Passos <rafael@rcpassos.me>
> ---
> Hi, I send the v1 for this patch only for the linux-doc list.
> The v2 fixes this, and has improvements to the commit message.
>
> It was reviewed and tested by Randy Dunlap.
> I decided to re-send since the original emails was not in picked by lore (not sure why).
> https://lore.kernel.org/intel-xe/1a20e4bf-fd7f-453e-b7a8-c7feb0b077c6@infradead.org/
>
> In case it helps, here are the tags Randy added in my first send:
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
Next time, please put these directly above the '---' along with your sign-off.
And please use the standard 'drm/xe:' tag in the subject.
I modified the subject and pushed it to drm-xe-next. Thanks for the patch.
>
> Thanks,
> Rafael Passos
>
> 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-07-03 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 1:20 [PATCH RESEND v2] Documentation: xe_drm: fix chars used for subsection Rafael Passos
2026-07-03 18:35 ` Rodrigo Vivi [this message]
2026-07-04 22:23 ` Rafael Passos
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=akgBC8A9h8nIyEYd@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=rafael@rcpassos.me \
--cc=rdunlap@infradead.org \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.