From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: manual merge of the v4l-dvb-next tree with the v4l-dvb tree
Date: Wed, 3 Jun 2020 12:38:03 +1000 [thread overview]
Message-ID: <20200603123803.7e97d3e8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Hi all,
Today's linux-next merge of the v4l-dvb-next tree got a conflict in:
drivers/staging/media/atomisp/pci/sh_css.c
between commit:
27333dadef57 ("media: atomisp: adjust some code at sh_css that could be broken")
from the v4l-dvb tree and commits:
815618c139d7 ("media: atomisp: fix pipeline initialization code")
be1fdab273a9 ("media: atomisp: change the detection of ISP2401 at runtime")
from the v4l-dvb-next tree.
I fixed it up (I used the version from the latter tree) 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.
Can you please make sure that the v4l-dvb tree and v4l-dvb-next tree
are ins sync? They share some patches that are not the same commits.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-06-03 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 2:38 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-23 0:51 linux-next: manual merge of the v4l-dvb-next tree with the v4l-dvb tree Stephen Rothwell
2019-04-23 8:12 ` Arnd Bergmann
2019-04-25 15:23 ` Mauro Carvalho Chehab
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=20200603123803.7e97d3e8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@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 NNTP newsgroup(s).