From: Alex Tran <alex.t.tran@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Alex Tran <alex.t.tran@gmail.com>
Subject: [PATCH] gpu: fix spacing and indentation in drm_gpuvm_sm_map_exec_lock description
Date: Sun, 10 Aug 2025 00:40:14 -0700 [thread overview]
Message-ID: <20250810074014.339366-1-alex.t.tran@gmail.com> (raw)
Fixes:
./Documentation/gpu/drm-mm:506: ./drivers/gpu/drm/drm_gpuvm.c:2444: ERROR: Unexpected indentation. [docutils]
./Documentation/gpu/drm-mm:506: ./drivers/gpu/drm/drm_gpuvm.c:2446: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
./Documentation/gpu/drm-mm:506: ./drivers/gpu/drm/drm_gpuvm.c:2450: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
./Documentation/gpu/drm-mm:506: ./drivers/gpu/drm/drm_gpuvm.c:2451: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
./Documentation/gpu/drm-mm:506: ./drivers/gpu/drm/drm_gpuvm.c:2455: ERROR: Unexpected indentation. [docutils]
Signed-off-by: Alex Tran <alex.t.tran@gmail.com>
---
drivers/gpu/drm/drm_gpuvm.c | 25 +++++++++++++++----------
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
index bbc7fecb6f4a..17dafa01700f 100644
--- a/drivers/gpu/drm/drm_gpuvm.c
+++ b/drivers/gpu/drm/drm_gpuvm.c
@@ -2441,21 +2441,26 @@ static const struct drm_gpuvm_ops lock_ops = {
* drm_exec_until_all_locked (&exec) {
* for_each_vm_bind_operation {
* switch (op->op) {
- * case DRIVER_OP_UNMAP:
- * ret = drm_gpuvm_sm_unmap_exec_lock(gpuvm, &exec, op->addr, op->range);
- * break;
- * case DRIVER_OP_MAP:
- * ret = drm_gpuvm_sm_map_exec_lock(gpuvm, &exec, num_fences,
- * op->addr, op->range,
- * obj, op->obj_offset);
- * break;
+ * case DRIVER_OP_UNMAP:
+ * ret = drm_gpuvm_sm_unmap_exec_lock(gpuvm, &exec, op->addr, op->range);
+ * break;
+ *
+ * case DRIVER_OP_MAP:
+ * ret = drm_gpuvm_sm_map_exec_lock(gpuvm, &exec, num_fences,
+ * op->addr, op->range,
+ * obj, op->obj_offset);
+ *
+ * break;
+ *
* }
*
* drm_exec_retry_on_contention(&exec);
- * if (ret)
- * return ret;
+ * if (ret) return ret;
+ *
* }
+ *
* }
+ *
* }
*
* This enables all locking to be performed before the driver begins modifying
--
2.34.1
reply other threads:[~2025-08-10 7:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250810074014.339366-1-alex.t.tran@gmail.com \
--to=alex.t.tran@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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
all inboxes | Powered by JetHome®