From: Nathan Lynch <nathan.lynch@amd.com>
To: Eder Zulian <ezulian@redhat.com>
Cc: <Basavaraj.Natikar@amd.com>, <vkoul@kernel.org>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: ptdma: Remove unused pointer dma_cmd_cache
Date: Mon, 14 Apr 2025 17:58:40 -0500 [thread overview]
Message-ID: <87v7r673kv.fsf@AUSNATLYNCH.amd.com> (raw)
In-Reply-To: <20250409114019.42026-1-ezulian@redhat.com>
Eder Zulian <ezulian@redhat.com> writes:
> The pointer 'struct kmem_cache *dma_cmd_cache' was introduced in commit
> b0b4a6b10577 ("dmaengine: ptdma: register PTDMA controller as a DMA
> resource") but it was never used.
>
> Signed-off-by: Eder Zulian <ezulian@redhat.com>
> ---
> drivers/dma/amd/ptdma/ptdma-dmaengine.c | 3 ---
> drivers/dma/amd/ptdma/ptdma.h | 1 -
> 2 files changed, 4 deletions(-)
>
> diff --git a/drivers/dma/amd/ptdma/ptdma-dmaengine.c b/drivers/dma/amd/ptdma/ptdma-dmaengine.c
> index 715ac3ae067b..3f7f6da05142 100644
> --- a/drivers/dma/amd/ptdma/ptdma-dmaengine.c
> +++ b/drivers/dma/amd/ptdma/ptdma-dmaengine.c
> @@ -656,8 +656,6 @@ int pt_dmaengine_register(struct pt_device *pt)
> kmem_cache_destroy(pt->dma_desc_cache);
>
> err_cache:
> - kmem_cache_destroy(pt->dma_cmd_cache);
> -
I think you could remove the 'err_cache' label and convert the users of it
to return -ENOMEM directly, since there aren't any unmanaged allocations
to unwind:
desc_cache_name = devm_kasprintf(pt->dev, GFP_KERNEL,
"%s-dmaengine-desc-cache",
dev_name(pt->dev));
if (!desc_cache_name) {
ret = -ENOMEM;
goto err_cache;
}
pt->dma_desc_cache = kmem_cache_create(desc_cache_name,
sizeof(struct pt_dma_desc), 0,
SLAB_HWCACHE_ALIGN, NULL);
if (!pt->dma_desc_cache) {
ret = -ENOMEM;
goto err_cache;
}
Otherwise LGTM.
next prev parent reply other threads:[~2025-04-14 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 11:40 [PATCH] dmaengine: ptdma: Remove unused pointer dma_cmd_cache Eder Zulian
2025-04-14 22:58 ` Nathan Lynch [this message]
2025-04-15 12:23 ` Eder Zulian
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=87v7r673kv.fsf@AUSNATLYNCH.amd.com \
--to=nathan.lynch@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=ezulian@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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