[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOesGMjVUCd9bN=pggS-ECjMR42b0SqXKewsp+NYFSVqRgSWrg@mail.gmail.com>
Date: Thu, 7 Nov 2019 10:27:20 -0800
From: Olof Johansson <olof@...om.net>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, Arnd Bergmann <arnd@...db.de>,
ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Xiaowei Bao <xiaowei.bao@....com>,
Hou Zhiqiang <Zhiqiang.Hou@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Fabio Estevam <festevam@...il.com>,
Shawn Guo <shawnguo@...nel.org>
Subject: Re: linux-next: manual merge of the pci tree with the arm-soc tree
On Wed, Nov 6, 2019 at 2:46 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> Today's linux-next merge of the pci tree got a conflict in:
>
> arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>
> between commit:
>
> 68e36a429ef5 ("arm64: dts: ls1028a: Move thermal-zone out of SoC")
>
> from the arm-soc tree and commit:
>
> 8d49ebe713ab ("arm64: dts: ls1028a: Add PCIe controller DT nodes")
Bjorn, we ask that driver subsystem maintainers don't pick up DT
changes since it causes conflicts like these.
Is it easy for you to drop this patch, or are we stuck with it?
Ideally it should never have been sent to you in the first place. :(
-Olof
Powered by blists - more mailing lists