From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Christian König" <christian.koenig@amd.com>
Subject: Re: [igt-dev] [PATCH 1/4] lib/amdgpu: rename function parameter
Date: Thu, 5 Jan 2023 15:29:01 +0100 [thread overview]
Message-ID: <Y7berZW1tpjYb3og@kamilkon-desk1> (raw)
In-Reply-To: <20230105005320.157831-1-vitaly.prosyak@amd.com>
Hi Vitaly,
On 2023-01-04 at 19:53:17 -0500, vitaly.prosyak@amd.com wrote:
> From: Vitaly Prosyak <vitaly.prosyak@amd.com>
>
> No functional change just cosmetic.
> Rename flags parameter to alloc_flags for clarity.
> There are mapping flags.
--^
Maybe put these in same sentence ?
>
> Signed-off-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
> ---
> lib/amdgpu/amd_memory.c | 10 ++++------
> lib/amdgpu/amd_memory.h | 2 +-
> 2 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/lib/amdgpu/amd_memory.c b/lib/amdgpu/amd_memory.c
> index 0aa400ac8..e3432a954 100644
> --- a/lib/amdgpu/amd_memory.c
> +++ b/lib/amdgpu/amd_memory.c
> @@ -41,7 +41,7 @@
> uint64_t size,
> uint64_t alignment,
> uint32_t type,
> - uint64_t flags,
> + uint64_t alloc_flags,
> uint64_t *vmc_addr,
> amdgpu_va_handle *va_handle)
> {
> @@ -49,7 +49,7 @@
> .alloc_size = size,
> .phys_alignment = alignment,
> .preferred_heap = type,
> - .flags = flags,
> + .flags = alloc_flags,
> };
> amdgpu_bo_handle buf_handle;
> int r;
> @@ -57,10 +57,8 @@
> r = amdgpu_bo_alloc(device_handle, &req, &buf_handle);
> igt_assert_eq(r, 0);
>
> - r = amdgpu_va_range_alloc(device_handle,
> - amdgpu_gpu_va_range_general,
> - size, alignment, 0, vmc_addr,
> - va_handle, 0);
> + r = amdgpu_va_range_alloc(device_handle, amdgpu_gpu_va_range_general,
> + size, alignment, 0, vmc_addr, va_handle, 0);
This is unrelated to description.
Regards,
Kamil
> igt_assert_eq(r, 0);
>
> r = amdgpu_bo_va_op(buf_handle, 0, size, *vmc_addr, 0, AMDGPU_VA_OP_MAP);
> diff --git a/lib/amdgpu/amd_memory.h b/lib/amdgpu/amd_memory.h
> index 77fd099b0..a06f88923 100644
> --- a/lib/amdgpu/amd_memory.h
> +++ b/lib/amdgpu/amd_memory.h
> @@ -35,7 +35,7 @@ gpu_mem_alloc(amdgpu_device_handle device_handle,
> uint64_t size,
> uint64_t alignment,
> uint32_t type,
> - uint64_t flags,
> + uint64_t alloc_flags,
> uint64_t *vmc_addr,
> amdgpu_va_handle *va_handle);
> int
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-01-05 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 0:53 [igt-dev] [PATCH 1/4] lib/amdgpu: rename function parameter vitaly.prosyak
2023-01-05 0:53 ` [igt-dev] [PATCH 2/4] lib/amdgpu: move function to another file vitaly.prosyak
2023-01-05 16:24 ` Kamil Konieczny
2023-01-06 2:55 ` vitaly prosyak
2023-01-05 0:53 ` [igt-dev] [PATCH 3/4] lib/amdgpu: add cp dma helper functions vitaly.prosyak
2023-01-05 16:48 ` Kamil Konieczny
2023-01-05 0:53 ` [igt-dev] [PATCH 4/4] tests/amdgpu: add cp dma tests vitaly.prosyak
2023-01-05 1:44 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [1/4] lib/amdgpu: rename function parameter Patchwork
2023-01-05 3:42 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-01-05 9:22 ` [igt-dev] [PATCH 1/4] " Christian König
2023-01-05 14:29 ` Kamil Konieczny [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-06 2:48 vitaly.prosyak
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=Y7berZW1tpjYb3og@kamilkon-desk1 \
--to=kamil.konieczny@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=igt-dev@lists.freedesktop.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