From: Sebastian Fricke <sebastian.fricke@collabora.com>
To: linux-media@vger.kernel.org
Subject: [GIT PULL FOR 6.10] MediaTek Vcodec mem free improvements
Date: Fri, 26 Apr 2024 10:59:39 +0200 [thread overview]
Message-ID: <20240426085939.cb5e4pcp5qoax67b@basti-XPS-13-9310> (raw)
Hey Hans & Mauro,
here is an older set from december 2023 that does a couple of
improvements on freeing buffers in the Vcodec driver.
Please pull.
The following changes since commit faa4364bef2ec0060de381ff028d1d836600a381:
media: stk1160: fix bounds checking in stk1160_copy_video() (2024-04-24 13:49:56 +0200)
are available in the Git repository at:
https://gitlab.collabora.com/sebastianfricke/linux.git tags/for-6.10-vcodec-mem-free
for you to fetch changes up to c8c81cce52b50328840c2bb240bfc8fc811a8006:
media: mediatek: vcodec: Only free buffer VA that is not NULL (2024-04-26 10:48:27 +0200)
----------------------------------------------------------------
A couple of improvements to mem free for the VCodec
----------------------------------------------------------------
Fei Shao (4):
media: mediatek: vcodec: Replace dev_name in error string
media: mediatek: vcodec: Drop unnecessary variable
media: mediatek: vcodec: Update mtk_vcodec_mem_free() error messages
media: mediatek: vcodec: Only free buffer VA that is not NULL
.../mediatek/vcodec/common/mtk_vcodec_util.c | 23 +++++++++++-----------
.../vcodec/decoder/vdec/vdec_av1_req_lat_if.c | 22 ++++++++++++++-------
.../mediatek/vcodec/encoder/venc/venc_h264_if.c | 5 +++--
3 files changed, 29 insertions(+), 21 deletions(-)
next reply other threads:[~2024-04-26 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 8:59 Sebastian Fricke [this message]
2024-04-26 10:04 ` [GIT PULL FOR 6.10] MediaTek Vcodec mem free improvements (#101239) Jenkins
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=20240426085939.cb5e4pcp5qoax67b@basti-XPS-13-9310 \
--to=sebastian.fricke@collabora.com \
--cc=linux-media@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).