From: broonie@kernel•org
To: Mauro Carvalho Chehab <mchehab@kernel•org>
Cc: "Hans Verkuil" <hverkuil-cisco@xs4all•nl>,
"Irui Wang" <irui.wang@mediatek•com>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>,
"Nícolas F . R . A . Prado" <nfraprado@collabora•com>
Subject: linux-next: manual merge of the v4l-dvb tree with the v4l-dvb-fixes tree
Date: Tue, 27 Sep 2022 13:34:10 +0100 [thread overview]
Message-ID: <20220927123410.342690-1-broonie@kernel.org> (raw)
Hi all,
Today's linux-next merge of the v4l-dvb tree got a conflict in:
drivers/media/platform/mediatek/vcodec/mtk_vcodec_enc_drv.c
between commit:
a2d2e593d39bc ("media: mediatek: vcodec: Drop platform_get_resource(IORESOURCE_IRQ)")
from the v4l-dvb-fixes tree and commit:
223afdf9caa07 ("media: mediatek: vcodec: Remove encoder driver get IRQ resource")
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/mediatek/vcodec/mtk_vcodec_enc_drv.c
index d2f5f30582a9c,0abe1dac75b3a..0000000000000
--- a/drivers/media/platform/mediatek/vcodec/mtk_vcodec_enc_drv.c
+++ b/drivers/media/platform/mediatek/vcodec/mtk_vcodec_enc_drv.c
next reply other threads:[~2022-09-27 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 12:34 broonie [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-06 0:19 linux-next: manual merge of the v4l-dvb tree with the v4l-dvb-fixes tree Stephen Rothwell
2020-01-09 0:10 Stephen Rothwell
2020-01-09 7:05 ` Mauro Carvalho Chehab
2017-06-05 2:03 Stephen Rothwell
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=20220927123410.342690-1-broonie@kernel.org \
--to=broonie@kernel$(echo .)org \
--cc=hverkuil-cisco@xs4all$(echo .)nl \
--cc=irui.wang@mediatek$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=nfraprado@collabora$(echo .)com \
/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