From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Greg KH <greg@kroah.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Cristiano Borges Cardoso <cristianoborgescardoso@gmail.com>,
Nishka Dasgupta <nishka.dasgupta@yahoo.com>,
Sanjana Sanikommu <sanjana99reddy99@gmail.com>,
Vatsala Narang <vatsalanarang@gmail.com>,
Bhanusree Pola <bhanusreemahesh@gmail.com>,
Himadri Pandya <himadri18.07@gmail.com>,
Jules Irenge <jbi.octave@gmail.com>
Subject: Re: linux-next: manual merge of the staging tree with the v4l-dvb tree
Date: Wed, 8 May 2019 11:54:36 +1000 [thread overview]
Message-ID: <20190508115436.43cd6bc0@canb.auug.org.au> (raw)
In-Reply-To: <20190426160658.4929d1ad@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
Hi all,
On Fri, 26 Apr 2019 16:06:58 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the staging tree got conflicts in:
>
> drivers/staging/media/zoran/Kconfig
> drivers/staging/media/zoran/videocodec.c
> drivers/staging/media/zoran/videocodec.h
> drivers/staging/media/zoran/zoran.h
> drivers/staging/media/zoran/zoran_card.c
> drivers/staging/media/zoran/zoran_card.h
> drivers/staging/media/zoran/zoran_device.c
> drivers/staging/media/zoran/zoran_device.h
> drivers/staging/media/zoran/zoran_driver.c
> drivers/staging/media/zoran/zoran_procfs.c
> drivers/staging/media/zoran/zoran_procfs.h
> drivers/staging/media/zoran/zr36016.c
> drivers/staging/media/zoran/zr36016.h
> drivers/staging/media/zoran/zr36050.c
> drivers/staging/media/zoran/zr36050.h
> drivers/staging/media/zoran/zr36057.h
> drivers/staging/media/zoran/zr36060.c
> drivers/staging/media/zoran/zr36060.h
>
> between commit:
>
> 8dce4b265a53 ("media: zoran: remove deprecated driver")
>
> from the v4l-dvb tree and various commits from the staging tree.
>
> I fixed it up (I just removed the files) 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.
This is now a conflict between the v4l-dvb tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-08 1:54 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 6:06 linux-next: manual merge of the staging tree with the v4l-dvb tree Stephen Rothwell
2019-04-27 6:36 ` Greg KH
2019-05-08 1:54 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-13 2:13 Stephen Rothwell
2023-02-13 7:05 ` Greg KH
2020-03-23 4:18 Stephen Rothwell
2020-03-23 9:56 ` Greg KH
2020-03-19 3:44 Stephen Rothwell
2020-03-19 8:30 ` Greg KH
2019-04-04 2:43 Stephen Rothwell
2018-12-10 5:53 Stephen Rothwell
2018-10-08 4:53 Stephen Rothwell
2018-10-08 4:47 Stephen Rothwell
2018-05-17 4:17 Stephen Rothwell
2018-05-17 7:22 ` Greg KH
2018-05-17 10:06 ` Mauro Carvalho Chehab
2018-05-26 4:45 ` Stephen Rothwell
2017-11-02 4:30 Stephen Rothwell
2017-04-11 3:32 Stephen Rothwell
2017-04-06 3:34 Stephen Rothwell
2017-04-06 18:58 ` Sean Young
2017-04-06 19:19 ` Greg KH
2017-04-06 20:39 ` Sean Young
2017-04-06 21:51 ` Stephen Rothwell
2017-02-06 4:31 Stephen Rothwell
2017-02-06 8:37 ` Greg KH
2016-03-04 5:24 Stephen Rothwell
2016-03-04 16:58 ` Greg KH
2015-05-11 5:28 Stephen Rothwell
2015-05-11 18:34 ` Greg KH
2015-03-24 5:29 Stephen Rothwell
2014-11-24 8:10 Stephen Rothwell
2014-11-24 8:09 Stephen Rothwell
2014-11-05 4:37 Stephen Rothwell
2014-11-05 4:31 Stephen Rothwell
2014-11-05 4:29 Stephen Rothwell
2014-11-06 2:19 ` Greg KH
2014-07-16 6:46 Stephen Rothwell
2014-07-16 20:52 ` Greg KH
2014-03-18 6:15 Stephen Rothwell
2014-03-17 7:55 Stephen Rothwell
2014-03-17 11:01 ` Mauro Carvalho Chehab
2014-03-17 18:29 ` Greg KH
[not found] ` < 20140317162937.2ccdec83@infradead.org>
2014-03-17 19:29 ` Mauro Carvalho Chehab
2014-03-17 22:27 ` Russell King
2014-03-19 15:30 ` Greg KH
2014-03-21 12:24 ` Grant Likely
2014-03-21 14:37 ` Grant Likely
2011-09-27 6:10 Stephen Rothwell
2011-09-27 14:18 ` Greg KH
2011-09-27 20:14 ` Paul Gortmaker
2011-07-16 13:03 Stephen Rothwell
2011-07-17 9:15 ` Greg KH
2011-03-04 5:39 Stephen Rothwell
2011-03-04 17:14 ` Greg KH
2011-03-04 5:39 Stephen Rothwell
2011-03-04 17:14 ` Greg KH
2011-03-04 5:39 Stephen Rothwell
2011-03-04 17:13 ` Greg KH
2011-03-04 17:54 ` Mauro Carvalho Chehab
2011-03-04 21:23 ` Greg KH
2011-03-04 22:17 ` Mauro Carvalho Chehab
2011-03-04 5:38 Stephen Rothwell
2011-03-04 17:12 ` Greg KH
2011-03-04 5:38 Stephen Rothwell
2011-03-04 17:13 ` Greg KH
2011-03-04 5:38 Stephen Rothwell
2011-03-04 17:12 ` Greg KH
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=20190508115436.43cd6bc0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bhanusreemahesh@gmail.com \
--cc=cristianoborgescardoso@gmail.com \
--cc=greg@kroah.com \
--cc=himadri18.07@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jbi.octave@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nishka.dasgupta@yahoo.com \
--cc=sanjana99reddy99@gmail.com \
--cc=vatsalanarang@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;
as well as URLs for NNTP newsgroup(s).