From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: tanze <tanze@kylinos.cn>,
mchehab@kernel.org, mingo@kernel.org, hverkuil@kernel.org,
tskd08@gmail.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] media: Optimize the code using vmalloc_array
Date: Mon, 3 Nov 2025 09:41:37 +0100 [thread overview]
Message-ID: <6f1cd703-7efe-4bd4-b236-b01bf1589b73@kernel.org> (raw)
In-Reply-To: <20251022032038.422230-1-tanze@kylinos.cn>
On 22/10/2025 05:20, tanze wrote:
> Change array_size() to vmalloc_array(), Due to vmalloc_array() is optimized better,
> uses fewer instructions, and handles overflow more concisely
>
> v1->v2: Update patch #02 #03 due to typos CI robot detected some issues
>
> v1:https://lore.kernel.org/all/20251021143122.268730-1-tanze@kylinos.cn/
>
> tanze (3):
> media: dvb-core: Optimize the code using vmalloc_array
> media: vivid: Optimize the code using vmalloc_array
> media: pt1: Optimize the code using vmalloc_array
FYI: all three patches are duplicates of:
https://lore.kernel.org/linux-media/20250812035310.497233-1-rongqianfeng@vivo.com/
which has already been merged.
So I'm skipping these patches.
Regards,
Hans
>
> drivers/media/dvb-core/dmxdev.c | 4 ++--
> drivers/media/dvb-core/dvb_demux.c | 9 +++++----
> drivers/media/pci/pt1/pt1.c | 2 +-
> drivers/media/test-drivers/vivid/vivid-core.c | 2 +-
> 4 files changed, 9 insertions(+), 8 deletions(-)
>
prev parent reply other threads:[~2025-11-03 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 3:20 tanze
2025-10-22 3:20 ` [PATCH v2 1/3] media: dvb-core: " tanze
2025-10-22 3:20 ` [PATCH v2 2/3] media: vivid: " tanze
2025-10-22 3:20 ` [PATCH v2 3/3] media: pt1: " tanze
2025-11-03 8:41 ` Hans Verkuil [this message]
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=6f1cd703-7efe-4bd4-b236-b01bf1589b73@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mingo@kernel.org \
--cc=tanze@kylinos.cn \
--cc=tskd08@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 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®