From: Javier Garcia <rampxxxx@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dakr@kernel.org, robin.clark@oss.qualcomm.com,
antomani103@gmail.com, dmitry.baryshkov@oss.qualcomm.com,
me@brighamcampbell.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Javier Garcia <rampxxxx@gmail.com>
Subject: [PATCH v3] drm: Add directive to format code in comment
Date: Sun, 10 Aug 2025 17:07:06 +0200 [thread overview]
Message-ID: <20250810150706.305040-1-rampxxxx@gmail.com> (raw)
In-Reply-To: <DBYS3FAEVMHC.178SXO45NIBI8@kernel.org>
Add formating directive line in function `drm_gpuvm_sm_map_exec_lock()`
comment to clear warning messages shown bellow that appears generating
documentation `make htmldocs`.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2444: Unexpected indentation.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2446: Block quote ends without a blank line; unexpected unindent.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2450: Definition list ends without a blank line; unexpected unindent.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2451: Definition list ends without a blank line; unexpected unindent.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2455: Unexpected indentation.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2456: Definition list ends without a blank line; unexpected unindent.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2457: Definition list ends without a blank line; unexpected unindent.
Warning: ./drivers/gpu/drm/drm_gpuvm.c:2458: Definition list ends without a blank line; unexpected unindent.
Fixes: 471920ce25d5 ("drm/gpuvm: Add locking helpers")
Signed-off-by: Javier Garcia <rampxxxx@gmail.com>
---
v2 -> v3:
* Added the proper imperative message.
* Fixes tag possition.
* v2 https://lore.kernel.org/lkml/20250810112218.293272-1-rampxxxx@gmail.com
v1 -> v2:
* Added the proper Fixes tag.
* v1 https://lore.kernel.org/lkml/20250804212902.22554-1-rampxxxx@gmail.com
drivers/gpu/drm/drm_gpuvm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
index bbc7fecb6f4a..74d949995a72 100644
--- a/drivers/gpu/drm/drm_gpuvm.c
+++ b/drivers/gpu/drm/drm_gpuvm.c
@@ -2432,6 +2432,8 @@ static const struct drm_gpuvm_ops lock_ops = {
*
* The expected usage is:
*
+ * .. code-block:: c
+ *
* vm_bind {
* struct drm_exec exec;
*
--
2.50.1
next prev parent reply other threads:[~2025-08-10 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 21:29 [PATCH] drm: Add directive to format code in comment Javier Garcia
2025-08-05 10:49 ` Dmitry Baryshkov
2025-08-05 11:51 ` Giant Sand Fans
2025-08-05 11:53 ` Giant Sand Fans
2025-08-05 16:55 ` Brigham Campbell
2025-08-05 17:55 ` Giant Sand Fans
2025-08-10 11:22 ` [PATCH v2] " Javier Garcia
2025-08-10 13:23 ` Danilo Krummrich
2025-08-10 14:12 ` Giant Sand Fans
2025-08-10 15:07 ` Javier Garcia [this message]
2025-08-11 1:04 ` [PATCH v3] " Bagas Sanjaya
2025-08-15 18:53 ` Danilo Krummrich
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=20250810150706.305040-1-rampxxxx@gmail.com \
--to=rampxxxx@gmail.com \
--cc=airlied@gmail.com \
--cc=antomani103@gmail.com \
--cc=dakr@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=me@brighamcampbell.com \
--cc=mripard@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).