From: Mark Brown <broonie@kernel•org>
To: Mauro Carvalho Chehab <mchehab@kernel•org>
Cc: Bryan O'Donoghue <bod@kernel•org>,
Dmitry Baryshkov <dmitry.baryshkov@oss•qualcomm.com>,
Hans Verkuil <hverkuil+cisco@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Neil Armstrong <neil.armstrong@linaro•org>,
Vishnu Reddy <busanna.reddy@oss•qualcomm.com>
Subject: linux-next: manual merge of the v4l-dvb tree with the origin tree
Date: Wed, 3 Jun 2026 14:33:03 +0100 [thread overview]
Message-ID: <aiAtD90wYV8-pibf@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
Hi all,
Today's linux-next merge of the v4l-dvb tree got a conflict in:
drivers/media/platform/qcom/iris/iris_vdec.c
between commit:
3d9593ad1a58c ("media: iris: fix use-after-free of fmt_src during MBPF check")
from the origin tree and commits:
65c06d2edded3 ("media: qcom: iris: vdec: allow GEN2 decoding into 10bit format")
56f93da11a7c3 ("media: iris: drop struct iris_fmt")
from the v4l-dvb tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc drivers/media/platform/qcom/iris/iris_vdec.c
index 99d544e2af4f9,a8d6354bee28f..0000000000000
--- a/drivers/media/platform/qcom/iris/iris_vdec.c
+++ b/drivers/media/platform/qcom/iris/iris_vdec.c
@@@ -61,23 -62,24 +62,18 @@@ int iris_vdec_inst_init(struct iris_ins
return iris_ctrls_init(inst);
}
- static const struct iris_fmt iris_vdec_formats_cap[] = {
- [IRIS_FMT_NV12] = {
- .pixfmt = V4L2_PIX_FMT_NV12,
- .type = V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE,
- },
- [IRIS_FMT_QC08C] = {
- .pixfmt = V4L2_PIX_FMT_QC08C,
- .type = V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE,
- },
-void iris_vdec_inst_deinit(struct iris_inst *inst)
-{
- kfree(inst->fmt_dst);
- kfree(inst->fmt_src);
-}
-
+ static const u32 iris_vdec_formats_cap[] = {
+ [IRIS_FMT_NV12] = V4L2_PIX_FMT_NV12,
+ [IRIS_FMT_QC08C] = V4L2_PIX_FMT_QC08C,
+ [IRIS_FMT_TP10] = V4L2_PIX_FMT_P010,
+ [IRIS_FMT_QC10C] = V4L2_PIX_FMT_QC10C,
};
- static const struct iris_fmt *
- find_format(struct iris_inst *inst, u32 pixfmt, u32 type)
+ static bool check_format(struct iris_inst *inst, u32 pixfmt, u32 type)
{
- const struct iris_fmt *fmt = NULL;
- unsigned int size = 0;
- unsigned int i;
+ unsigned int size, i;
+ const u32 *fmt;
+
switch (type) {
case V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE:
fmt = inst->core->iris_platform_data->inst_iris_fmts;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-06-03 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 13:33 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-02 16:16 linux-next: manual merge of the v4l-dvb tree with the origin tree Mark Brown
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=aiAtD90wYV8-pibf@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=bod@kernel$(echo .)org \
--cc=busanna.reddy@oss$(echo .)qualcomm.com \
--cc=dmitry.baryshkov@oss$(echo .)qualcomm.com \
--cc=hverkuil+cisco@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=neil.armstrong@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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