From: "Christian König" <christian.koenig@amd.com>
To: Kunwu Chan <chentao@kylinos.cn>,
alexander.deucher@amd.com, Xinhui.Pan@amd.com, airlied@gmail.com,
daniel@ffwll.ch
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] drm/amdgpu: Use KMEM_CACHE instead of kmem_cache_create
Date: Wed, 21 Feb 2024 11:57:57 +0100 [thread overview]
Message-ID: <75a4102e-b078-4e95-a5b5-a677ad9622fd@amd.com> (raw)
In-Reply-To: <20240221095907.172408-1-chentao@kylinos.cn>
Am 21.02.24 um 10:59 schrieb Kunwu Chan:
> For where the cache name and the structure name match.
> Use the new KMEM_CACHE() macro instead of direct kmem_cache_create
> to simplify the creation of SLAB caches.
Reviewed-by: Christian König <christian.koenig@amd.com> for the entire
series.
>
> Kunwu Chan (3):
> drm/amdgpu: Simplify the allocation of fence slab caches
> drm/amdgpu: Simplify the allocation of mux_chunk slab caches
> drm/amdgpu: Simplify the allocation of sync slab caches
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 4 +---
> drivers/gpu/drm/amd/amdgpu/amdgpu_ring_mux.c | 4 +---
> drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c | 4 +---
> 3 files changed, 3 insertions(+), 9 deletions(-)
>
next prev parent reply other threads:[~2024-02-21 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 9:59 Kunwu Chan
2024-02-21 9:59 ` [PATCH 1/3] drm/amdgpu: Simplify the allocation of fence slab caches Kunwu Chan
2024-02-21 9:59 ` [PATCH 2/3] drm/amdgpu: Simplify the allocation of mux_chunk " Kunwu Chan
2024-02-21 9:59 ` [PATCH 3/3] drm/amdgpu: Simplify the allocation of sync " Kunwu Chan
2024-02-21 10:57 ` Christian König [this message]
2024-02-21 20:34 ` [PATCH 0/3] drm/amdgpu: Use KMEM_CACHE instead of kmem_cache_create Alex Deucher
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=75a4102e-b078-4e95-a5b5-a677ad9622fd@amd.com \
--to=christian.koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chentao@kylinos.cn \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®