| Message ID | 20210216130449.3d1f0338@canb.auug.org.au (mailing list archive) |
|---|---|
| State | Not Applicable |
| Headers | show |
| Series | linux-next: manual merge of the net-next tree with the arm-soc tree | expand |
| Context | Check | Description |
|---|---|---|
| netdev/tree_selection | success | Not a local patch |
Hi, > -----Original Message----- > From: Stephen Rothwell [mailto:sfr@canb.auug.org.au] > Sent: Tuesday, February 16, 2021 11:05 AM > To: David Miller <davem@davemloft.net>; Networking <netdev@vger.kernel.org>; Olof Johansson <olof@lixom.net>; Arnd > Bergmann <arnd@arndb.de>; ARM <linux-arm-kernel@lists.infradead.org> > Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Linux > Next Mailing List <linux-next@vger.kernel.org>; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) > <nobuhiro1.iwamatsu@toshiba.co.jp> > Subject: linux-next: manual merge of the net-next tree with the arm-soc tree > > Hi all, > > Today's linux-next merge of the net-next tree got conflicts in: > > arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > arch/arm64/boot/dts/toshiba/tmpv7708.dtsi > > between commits: > > 4fd18fc38757 ("arm64: dts: visconti: Add watchdog support for TMPV7708 SoC") > 0109a17564fc ("arm: dts: visconti: Add DT support for Toshiba Visconti5 GPIO driver") > > from the arm-soc tree and commit: > > ec8a42e73432 ("arm: dts: visconti: Add DT support for Toshiba Visconti5 ethernet controller") > > from the net-next 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. > This is because the DTS changes are included in net-next. This patch should be merged via the soc tree. I had the same problem before. How is it correct to send a DTS patch? Should I separate into different series? Best regards, Nobuhiro
On Tue, Feb 16, 2021 at 3:20 AM <nobuhiro1.iwamatsu@toshiba.co.jp> wrote: > > > > 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. > > > > This is because the DTS changes are included in net-next. This patch should be merged via the soc tree. > I had the same problem before. How is it correct to send a DTS patch? > Should I separate into different series? I have already sent the pull requests for the dts files to Linus, so that's not changing any more for this time, and he will just have to fix it up when he pulls both branches. In the future, please send all dts updates to soc@kernel.org (after the binding and driver is merged) rather than together with the device drivers. Sending the devicetree binding updates is a little trickier, as we tend to want them merged both with the driver and the dts files. One way to do this is to have a shared branch for the bindings updates, and then base both the driver branch and the dts branch on top of the same commits for that. A simpler alternative is to merge only the driver and binding changes in one release, and send the dts changes for the following release. This obviously takes longer to complete. Arnd
Hi, > From: Stephen Rothwell, Sent: Tuesday, February 16, 2021 11:05 AM <snip> > diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > index 2407b2d89c1e,48fa8776e36f..000000000000 > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > @@@ -42,11 -42,20 +42,29 @@@ > clock-names = "apb_pclk"; > }; > > +&wdt { > + status = "okay"; > + clocks = <&wdt_clk>; > +}; > + > +&gpio { > + status = "okay"; > ++};` This ` causes the following build error on the next-20210216. DTC arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb Error: arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts:52.3-4 syntax error FATAL ERROR: Unable to parse input tree scripts/Makefile.lib:336: recipe for target 'arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb' failed make[2]: *** [arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb] Error 1 scripts/Makefile.build:530: recipe for target 'arch/arm64/boot/dts/toshiba' failed Best regards, Yoshihiro Shimoda
On Tue, 16 Feb 2021 at 17:26, Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> wrote: > > Hi, > > > From: Stephen Rothwell, Sent: Tuesday, February 16, 2021 11:05 AM > <snip> > > diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > index 2407b2d89c1e,48fa8776e36f..000000000000 > > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > @@@ -42,11 -42,20 +42,29 @@@ > > clock-names = "apb_pclk"; > > }; > > > > +&wdt { > > + status = "okay"; > > + clocks = <&wdt_clk>; > > +}; > > + > > +&gpio { > > + status = "okay"; > > ++};` > LKFT builders also found this problem while building arm64 dtb. > This ` causes the following build error on the next-20210216. > > DTC arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb > Error: arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts:52.3-4 syntax error > FATAL ERROR: Unable to parse input tree > scripts/Makefile.lib:336: recipe for target 'arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb' failed > make[2]: *** [arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb] Error 1 > scripts/Makefile.build:530: recipe for target 'arch/arm64/boot/dts/toshiba' failed ref: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/jobs/1033072509#L382 - Naresh
Hi, Thnaks for your report. > LKFT builders also found this problem while building arm64 dtb. > > > This ` causes the following build error on the next-20210216. > > > > DTC arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb > > Error: arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts:52.3-4 syntax error > > FATAL ERROR: Unable to parse input tree > > scripts/Makefile.lib:336: recipe for target 'arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb' failed > > make[2]: *** [arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb] Error 1 > > scripts/Makefile.build:530: recipe for target 'arch/arm64/boot/dts/toshiba' failed > > ref: > https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/jobs/1033072509#L382 > This seems to be a problem fixing the conflict. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c5e188ea08290d9b6625b4bef322012c0b1902d7 ``` diff --git a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts index 2407b2d89c1e9..3760df93a89b5 100644 --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts @@ -49,4 +49,22 @@ &gpio { status = "okay"; +};` + +&piether { + status = "okay"; + phy-handle = <&phy0>; + phy-mode = "rgmii-id"; + clocks = <&clk300mhz>, <&clk125mhz>; + clock-names = "stmmaceth", "phy_ref_clk"; + + mdio0 { + #address-cells = <1>; + #size-cells = <0>; + compatible = "snps,dwmac-mdio"; + phy0: ethernet-phy@1 { + device_type = "ethernet-phy"; + reg = <0x1>; + }; + }; }; ``` Stephen, could you fix this? Best regards, Nobuhiro
Hi, I attached a patch which revise this issue. If I need to send with git send-email, please let me know. Best regards, Nobuhiro > -----Original Message----- > From: iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) > Sent: Tuesday, February 16, 2021 10:47 PM > To: Naresh Kamboju <naresh.kamboju@linaro.org>; Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>; Stephen > Rothwell <sfr@canb.auug.org.au> > Cc: David Miller <davem@davemloft.net>; Networking <netdev@vger.kernel.org>; Olof Johansson <olof@lixom.net>; Arnd > Bergmann <arnd@arndb.de>; ARM <linux-arm-kernel@lists.infradead.org>; Bartosz Golaszewski > <bgolaszewski@baylibre.com>; Linux Next Mailing List <linux-next@vger.kernel.org>; Linux Kernel Mailing List > <linux-kernel@vger.kernel.org>; lkft-triage@lists.linaro.org > Subject: RE: linux-next: manual merge of the net-next tree with the arm-soc tree > > Hi, > > Thnaks for your report. > > > LKFT builders also found this problem while building arm64 dtb. > > > > > This ` causes the following build error on the next-20210216. > > > > > > DTC arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb > > > Error: arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts:52.3-4 syntax error > > > FATAL ERROR: Unable to parse input tree > > > scripts/Makefile.lib:336: recipe for target 'arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb' failed > > > make[2]: *** [arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb] Error 1 > > > scripts/Makefile.build:530: recipe for target 'arch/arm64/boot/dts/toshiba' failed > > > > ref: > > https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/jobs/1033072509#L382 > > > > This seems to be a problem fixing the conflict. > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c5e188ea08290d9b6625b4bef322012c0b > 1902d7 > > ``` > diff --git a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > index 2407b2d89c1e9..3760df93a89b5 100644 > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > @@ -49,4 +49,22 @@ > > &gpio { > status = "okay"; > +};` > + > +&piether { > + status = "okay"; > + phy-handle = <&phy0>; > + phy-mode = "rgmii-id"; > + clocks = <&clk300mhz>, <&clk125mhz>; > + clock-names = "stmmaceth", "phy_ref_clk"; > + > + mdio0 { > + #address-cells = <1>; > + #size-cells = <0>; > + compatible = "snps,dwmac-mdio"; > + phy0: ethernet-phy@1 { > + device_type = "ethernet-phy"; > + reg = <0x1>; > + }; > + }; > }; > ``` > > Stephen, could you fix this? > > Best regards, > Nobuhiro
Hi Yoshihiro, On Tue, 16 Feb 2021 11:53:56 +0000 Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> wrote: > > > From: Stephen Rothwell, Sent: Tuesday, February 16, 2021 11:05 AM > <snip> > > diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > index 2407b2d89c1e,48fa8776e36f..000000000000 > > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > @@@ -42,11 -42,20 +42,29 @@@ > > clock-names = "apb_pclk"; > > }; > > > > +&wdt { > > + status = "okay"; > > + clocks = <&wdt_clk>; > > +}; > > + > > +&gpio { > > + status = "okay"; > > ++};` > > This ` causes the following build error on the next-20210216. > > DTC arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb > Error: arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts:52.3-4 syntax error > FATAL ERROR: Unable to parse input tree > scripts/Makefile.lib:336: recipe for target 'arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb' failed > make[2]: *** [arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb] Error 1 > scripts/Makefile.build:530: recipe for target 'arch/arm64/boot/dts/toshiba' failed Sorry about that ( ` is nect to ESC on my keyboard) it will be fixed up in today's resolution.
Hi Stephen, > From: Stephen Rothwell, Sent: Wednesday, February 17, 2021 6:18 AM > On Tue, 16 Feb 2021 11:53:56 +0000 Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> wrote: > > > > > From: Stephen Rothwell, Sent: Tuesday, February 16, 2021 11:05 AM > > <snip> > > > diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > > index 2407b2d89c1e,48fa8776e36f..000000000000 > > > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > > @@@ -42,11 -42,20 +42,29 @@@ > > > clock-names = "apb_pclk"; > > > }; > > > > > > +&wdt { > > > + status = "okay"; > > > + clocks = <&wdt_clk>; > > > +}; > > > + > > > +&gpio { > > > + status = "okay"; > > > ++};` > > > > This ` causes the following build error on the next-20210216. > > > > DTC arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb > > Error: arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts:52.3-4 syntax error > > FATAL ERROR: Unable to parse input tree > > scripts/Makefile.lib:336: recipe for target 'arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb' failed > > make[2]: *** [arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dtb] Error 1 > > scripts/Makefile.build:530: recipe for target 'arch/arm64/boot/dts/toshiba' failed > > Sorry about that ( ` is nect to ESC on my keyboard) it will be fixed up > in today's resolution. Thank you for the reply! I understood it. Best regards, Yoshihiro Shimoda
diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts index 2407b2d89c1e,48fa8776e36f..000000000000 --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts diff --cc arch/arm64/boot/dts/toshiba/tmpv7708.dtsi index 4264f3e6ac9c,3366786699fc..000000000000 --- a/arch/arm64/boot/dts/toshiba/tmpv7708.dtsi
Hi all, Today's linux-next merge of the net-next tree got conflicts in: arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts arch/arm64/boot/dts/toshiba/tmpv7708.dtsi between commits: 4fd18fc38757 ("arm64: dts: visconti: Add watchdog support for TMPV7708 SoC") 0109a17564fc ("arm: dts: visconti: Add DT support for Toshiba Visconti5 GPIO driver") from the arm-soc tree and commit: ec8a42e73432 ("arm: dts: visconti: Add DT support for Toshiba Visconti5 ethernet controller") from the net-next 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.