From: rui.zhang@intel.com (Zhang Rui)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the thermal tree with the imx-mxs tree
Date: Wed, 18 Oct 2017 09:47:26 +0800 [thread overview]
Message-ID: <1508291246.2746.41.camel@intel.com> (raw)
In-Reply-To: <20171016091728.gbtoakghi4ndyyt2@sirena.co.uk>
Hi, Mark,
thanks for the fix.
On Mon, 2017-10-16 at 10:17 +0100, Mark Brown wrote:
> Hi Zhang,
>
> Today's linux-next merge of the thermal tree got a conflict in:
>
> ? arch/arm/boot/dts/imx6ul.dtsi
>
> between commit:
>
> ???efb9adb274754 ("ARM: dts: imx6ul: Remove leading zeroes from unit
> addresses")
>
> from the imx-mxs tree and commit:
>
> ???1dc31d4981dd9 ("ARM: dts: imx6ul: Add imx6ul-tempmon")
>
> from the thermal 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.??Usually DTS changes go through arm-soc to avoid
> issues like this.
Shawn,
https://patchwork.kernel.org/patch/9841191/
https://patchwork.kernel.org/patch/9841193/
Should I drop these two dts patches and leave them to you?
thanks,
rui
>
> diff --cc arch/arm/boot/dts/imx6ul.dtsi
> index 2057ee695a66,51717d54f285..000000000000
> --- a/arch/arm/boot/dts/imx6ul.dtsi
> +++ b/arch/arm/boot/dts/imx6ul.dtsi
> @@@ -860,13 -869,23 +869,23 @@@
> ?? reg = <0x021b0000 0x4000>;
> ?? };
> ??
> ?- ocotp: ocotp-ctrl at 021bc000 {
> ?+ ocotp: ocotp-ctrl at 21bc000 {
> +? #address-cells = <1>;
> +? #size-cells = <1>;
> ?? compatible = "fsl,imx6ul-ocotp",
> "syscon";
> ?? reg = <0x021bc000 0x4000>;
> ?? clocks = <&clks IMX6UL_CLK_OCOTP>;
> +?
> +? tempmon_calib: calib at 38 {
> +? reg = <0x38 4>;
> +? };
> +?
> +? tempmon_temp_grade: temp-grade at 20 {
> +? reg = <0x20 4>;
> +? };
> ?? };
> ??
> ?- lcdif: lcdif at 021c8000 {
> ?+ lcdif: lcdif at 21c8000 {
> ?? compatible = "fsl,imx6ul-lcdif",
> "fsl,imx28-lcdif";
> ?? reg = <0x021c8000 0x4000>;
> ?? interrupts = <GIC_SPI 5
> IRQ_TYPE_LEVEL_HIGH>;
next parent reply other threads:[~2017-10-18 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171016091728.gbtoakghi4ndyyt2@sirena.co.uk>
2017-10-18 1:47 ` Zhang Rui [this message]
2017-10-18 2:19 ` linux-next: manual merge of the thermal tree with the imx-mxs tree Shawn Guo
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=1508291246.2746.41.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).