From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
karol.wachowski@linux.intel.com, lizhi.hou@amd.com
Subject: Re: [PATCH] accel/ivpu: Make BO free helper NULL-safe
Date: Thu, 24 Sep 2026 13:12:42 +0200 [thread overview]
Message-ID: <cf0db8d5-1a88-4eb9-bf67-08585de9342f@linux.intel.com> (raw)
In-Reply-To: <20260924105906.489378-1-andrzej.kacprowski@linux.intel.com>
On 2026-09-24 12:59 PM, Andrzej Kacprowski wrote:
> Handle NULL buffers in ivpu_bo_free() so callers can use it as a
> kfree-like cleanup helper.
>
> Use the NULL-safe helper to simplify error paths and teardown code in
> firmware, IPC, preemption buffer, and metric streamer cleanup. This
> removes redundant conditional frees and collapses unwind labels that only
> differed by which BOs had been allocated.
Reviewed-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>>
Signed-off-by: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
> ---
> drivers/accel/ivpu/ivpu_fw.c | 65 +++++++++++++++--------------------
> drivers/accel/ivpu/ivpu_gem.c | 3 ++
> drivers/accel/ivpu/ivpu_ipc.c | 11 +++---
> drivers/accel/ivpu/ivpu_job.c | 6 ++--
> drivers/accel/ivpu/ivpu_ms.c | 17 ++++-----
> 5 files changed, 44 insertions(+), 58 deletions(-)
next prev parent reply other threads:[~2026-09-24 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 10:59 [PATCH] accel/ivpu: Make BO free helper NULL-safe Andrzej Kacprowski
2026-09-24 11:12 ` Dawid Osuchowski [this message]
2026-09-28 6:29 ` Wachowski, Karol
2026-09-28 5:54 ` Wachowski, Karol
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=cf0db8d5-1a88-4eb9-bf67-08585de9342f@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=andrzej.kacprowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=karol.wachowski@linux.intel.com \
--cc=lizhi.hou@amd.com \
--cc=oded.gabbay@gmail.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.