From: Detlev Casanova <detlev.casanova@collabora.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>,
Heiko Stuebner <heiko@sntech.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: linux-next: manual merge of the scsi tree with the rockchip tree
Date: Tue, 11 Mar 2025 12:24:25 -0400 [thread overview]
Message-ID: <6134949.lOV4Wx5bFT@earth> (raw)
In-Reply-To: <20250311183524.38989e83@canb.auug.org.au>
Hi Stephen,
On Tuesday, 11 March 2025 03:35:24 EDT Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the scsi tree got a conflict in:
>
> arch/arm64/boot/dts/rockchip/rk3576.dtsi
>
> between commit:
>
> 36299757129c ("arm64: dts: rockchip: Add SFC nodes for rk3576")
>
> from the rockchip tree and commit:
>
> c75e5e010fef ("scsi: arm64: dts: rockchip: Add UFS support for RK3576
> SoC")
>
> from the scsi 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.
Unfortunately, this fix is incorrect as nodes must be in address order, so
ufshc: ufshc@2a2d0000 must be above sfc1: spi@2a300000.
As we are close the the merge window, I won't mind if the patches have to be
postponed to the next cycle, but some device trees won't build anymore.
This can also be left as is with a new patch to fix the order (to be backported
if needed)
Regards,
Detlev.
next prev parent reply other threads:[~2025-03-11 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 7:35 linux-next: manual merge of the scsi tree with the rockchip tree Stephen Rothwell
2025-03-11 16:24 ` Detlev Casanova [this message]
2025-03-11 21:51 ` Stephen Rothwell
2025-03-12 7:03 ` Heiko Stuebner
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=6134949.lOV4Wx5bFT@earth \
--to=detlev.casanova@collabora.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=shawn.lin@rock-chips.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).