From: Frank Li <Frank.li@nxp.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-media@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-hardening@vger.kernel.org, gustavoars@kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
"open list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<imx@lists.linux.dev>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: nxp: imx8-isi: remove kzalloc_objs
Date: Fri, 6 Mar 2026 00:11:33 -0500 [thread overview]
Message-ID: <aapiBcnPHa3eDLN5@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260306044536.149204-1-rosenp@gmail.com>
On Thu, Mar 05, 2026 at 08:45:36PM -0800, Rosen Penev wrote:
Subjest: use flexible array to fix memory leak
> Use a flexible arraay member to combine allocations.
typo arraay
>
> It looks like pipes never gets freed anywhere. Meaning this effectively
> fixes a memory leak.
Remove "It looks like". The pipes never ...
Because fix memory leak, need fixes tag here.
Frank
>
next prev parent reply other threads:[~2026-03-06 5:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 4:45 [PATCH] media: nxp: imx8-isi: remove kzalloc_objs Rosen Penev
2026-03-06 5:11 ` Frank Li [this message]
2026-03-06 6:19 ` Rosen Penev
2026-03-06 6:56 ` Marc Kleine-Budde
2026-03-06 6:59 ` Rosen Penev
2026-03-06 7:04 ` Marc Kleine-Budde
2026-03-19 22:09 ` Laurent Pinchart
2026-03-20 0:11 ` Rosen Penev
2026-03-20 0:57 ` Laurent Pinchart
2026-03-20 1:06 ` Rosen Penev
2026-03-20 10:16 ` Laurent Pinchart
2026-03-20 18:15 ` Kees Cook
2026-03-26 1:53 ` Rosen Penev
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=aapiBcnPHa3eDLN5@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=festevam@gmail.com \
--cc=gustavoars@kernel.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rosenp@gmail.com \
--cc=s.hauer@pengutronix.de \
/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