From: "Timur Kristóf" <timur.kristof@gmail.com>
To: amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, christian.koenig@amd.com,
"Timur Kristóf" <timur.kristof@gmail.com>
Subject: [PATCH 2/4] drm/amdgpu: Clarify that BO size is in bytes in comments
Date: Mon, 1 Sep 2025 12:00:10 +0200 [thread overview]
Message-ID: <20250901100012.439155-2-timur.kristof@gmail.com> (raw)
In-Reply-To: <20250901100012.439155-1-timur.kristof@gmail.com>
To avoid confusion with dwords.
Signed-off-by: Timur Kristóf <timur.kristof@gmail.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
index 122a88294883..9ffadc029ef8 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
@@ -220,7 +220,7 @@ void amdgpu_bo_placement_from_domain(struct amdgpu_bo *abo, u32 domain)
* amdgpu_bo_create_reserved - create reserved BO for kernel use
*
* @adev: amdgpu device object
- * @size: size for the new BO
+ * @size: size for the new BO in bytes
* @align: alignment for the new BO
* @domain: where to place it
* @bo_ptr: used to initialize BOs in structures
@@ -317,7 +317,7 @@ int amdgpu_bo_create_reserved(struct amdgpu_device *adev,
* amdgpu_bo_create_kernel - create BO for kernel use
*
* @adev: amdgpu device object
- * @size: size for the new BO
+ * @size: size for the new BO in bytes
* @align: alignment for the new BO
* @domain: where to place it
* @bo_ptr: used to initialize BOs in structures
--
2.51.0
next prev parent reply other threads:[~2025-09-01 10:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 10:00 [PATCH 1/4] drm/amdgpu: Fix allocating extra dwords for rings Timur Kristóf
2025-09-01 10:00 ` Timur Kristóf [this message]
2025-09-02 6:43 ` [PATCH 2/4] drm/amdgpu: Clarify that BO size is in bytes in comments Christian König
2025-09-02 8:08 ` Timur Kristóf
2025-09-02 11:10 ` Christian König
2025-09-02 11:28 ` Timur Kristóf
2025-09-01 10:00 ` [PATCH 3/4] drm/amdgpu: Fill extra dwords with NOPs Timur Kristóf
2025-09-01 10:13 ` Tvrtko Ursulin
2025-09-02 11:30 ` Timur Kristóf
2025-09-02 11:34 ` Christian König
2025-09-02 11:39 ` Tvrtko Ursulin
2025-09-02 6:39 ` Christian König
2025-09-02 7:42 ` Timur Kristóf
2025-09-02 9:54 ` Christian König
2025-09-02 10:10 ` Timur Kristóf
2025-09-01 10:00 ` [PATCH 4/4] drm/amdgpu: Set SDMA v3 copy_max_bytes to 0x3fff00 Timur Kristóf
2025-09-02 6:45 ` Christian König
2025-09-02 7:52 ` Timur Kristóf
2025-09-02 6:41 ` [PATCH 1/4] drm/amdgpu: Fix allocating extra dwords for rings Christian König
2025-09-02 8:26 ` Timur Kristóf
2025-09-02 11:20 ` Christian König
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=20250901100012.439155-2-timur.kristof@gmail.com \
--to=timur.kristof@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
/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.