From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Jai Luthra <jai.luthra@ideasonboard.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Romain Gantois <romain.gantois@bootlin.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: linux-next: manual merge of the v4l-dvb tree with the i2c tree
Date: Tue, 29 Apr 2025 14:46:24 +0300 [thread overview]
Message-ID: <9918a4e1-e3fa-4577-ac06-46efeab12507@ideasonboard.com> (raw)
In-Reply-To: <20250428113052.38cf10da@canb.auug.org.au>
Hi,
On 28/04/2025 04:30, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 28 Apr 2025 11:22:00 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> On Mon, 28 Apr 2025 10:49:05 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>
>>> Today's linux-next merge of the v4l-dvb tree got a conflict in:
>>>
>>> drivers/media/i2c/ds90ub960.c
>>>
>>> between commits:
>>>
>>> 3ec29d51b546 ("media: i2c: ds90ub960: Protect alias_use_mask with a mutex")
>>> 818bd489f137 ("i2c: use client addresses directly in ATR interface")
>>>
>>> from the i2c tree and commits:
>>>
>>> 24868501a744 ("media: i2c: ds90ub9xx: Add err parameter to read/write funcs")
>>> 2ca499384e98 ("media: i2c: ds90ub960: Add RX port iteration support")
>>>
>>> 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.
>>
>> The actual resolution is below ...
>
> I hit the wrong key :-( Resolution below.
I came up with the same resolution, so looks correct to me.
Tomi
next prev parent reply other threads:[~2025-04-29 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 0:49 linux-next: manual merge of the v4l-dvb tree with the i2c tree Stephen Rothwell
2025-04-28 1:22 ` Stephen Rothwell
2025-04-28 1:30 ` Stephen Rothwell
2025-04-29 11:46 ` Tomi Valkeinen [this message]
2025-05-29 2:49 ` Stephen Rothwell
2025-05-30 8:13 ` Romain Gantois
2025-05-30 11:24 ` Wolfram Sang
2025-06-02 16:17 ` Romain Gantois
2025-05-31 12:05 ` Wolfram Sang
2025-06-02 15:57 ` Romain Gantois
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 1:12 Stephen Rothwell
2013-05-01 3:27 ` 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=9918a4e1-e3fa-4577-ac06-46efeab12507@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=jai.luthra@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.