From: Ian Campbell <ian.campbell@citrix.com>
To: Rob Herring <robherring2@gmail.com>, "arm@kernel.org" <arm@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Russell King <linux@arm.linux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Kristina Martsenko <kristina.martsenko@arm.com>,
Kevin Hilman <khilman@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH v5] dtb: Create a common home for cross-architecture dtsi files.
Date: Sun, 16 Aug 2015 10:01:11 +0100 [thread overview]
Message-ID: <1439715671.3480.21.camel@citrix.com> (raw)
In-Reply-To: <CAL_JsqKv2aOEM-U7JNZnaHomA6HFBSFhSLZ-zhp7c20s6gQBaQ@mail.gmail.com>
On Fri, 2015-08-14 at 16:21 -0500, Rob Herring wrote:
> +arm-soc
I could've sworn I did the same at one point. Obviously not.
>
> On Tue, Aug 11, 2015 at 5:07 AM, Ian Campbell <
> ian.campbell@citrix.com> wrote:
> > On Mon, 2015-08-03 at 17:06 +0100, Ian Campbell wrote:
> > > Commit 9ccd608070b6 ("arm64: dts: add device tree for ARM SMM
> > > -A53x2 on
> > > LogicTile Express 20MG") added a new dts file to arch/arm64 which
> > > included "../../../../arm/boot/dts/vexpress-v2m-rs1.dtsi", i.e. a
> > > .dtsi supplied by arch/arm.
> > >
> > > Unfortunately this causes some issues for the split device tree
> > > repository[0], since things get moved around there. In that
> > > context
> > > the new .dts ends up at src/arm64/arm/vexpress-v2f-1xv7
> > > -ca53x2.dts
> > > while the include is at src/arm/vexpress-v2m-rs1.dtsi.
> >
> > Hi Grant,
> >
> > Do you think there is any chance of getting this into 4.2-rc$NEXT
> > or shall
> > we wait until 4.3? I'm assuming this should go via the DT tree, but
> > maybe
> > it should go via an ARM tree?
>
> I was assuming this would go thru the arm-soc tree which is why I
> acked it. It is getting a bit late for 4.2 at this point, but I guess
> the standalone tree remains broken for these platforms until this is
> done.
Correct.
> Probably not such a big deal in grand scheme of things.
I guess not. FWIW I've not pushed since the breakage started happening,
so the split tree isn't broken, but it's also now however many weeks
behind. Once 4.3-rc1 arrives with this fixed I'll push all the 4.2-rcN
and 4.2 as well.
Ian.
WARNING: multiple messages have this Message-ID (diff)
From: ian.campbell@citrix.com (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] dtb: Create a common home for cross-architecture dtsi files.
Date: Sun, 16 Aug 2015 10:01:11 +0100 [thread overview]
Message-ID: <1439715671.3480.21.camel@citrix.com> (raw)
In-Reply-To: <CAL_JsqKv2aOEM-U7JNZnaHomA6HFBSFhSLZ-zhp7c20s6gQBaQ@mail.gmail.com>
On Fri, 2015-08-14 at 16:21 -0500, Rob Herring wrote:
> +arm-soc
I could've sworn I did the same at one point. Obviously not.
>
> On Tue, Aug 11, 2015 at 5:07 AM, Ian Campbell <
> ian.campbell at citrix.com> wrote:
> > On Mon, 2015-08-03 at 17:06 +0100, Ian Campbell wrote:
> > > Commit 9ccd608070b6 ("arm64: dts: add device tree for ARM SMM
> > > -A53x2 on
> > > LogicTile Express 20MG") added a new dts file to arch/arm64 which
> > > included "../../../../arm/boot/dts/vexpress-v2m-rs1.dtsi", i.e. a
> > > .dtsi supplied by arch/arm.
> > >
> > > Unfortunately this causes some issues for the split device tree
> > > repository[0], since things get moved around there. In that
> > > context
> > > the new .dts ends up at src/arm64/arm/vexpress-v2f-1xv7
> > > -ca53x2.dts
> > > while the include is at src/arm/vexpress-v2m-rs1.dtsi.
> >
> > Hi Grant,
> >
> > Do you think there is any chance of getting this into 4.2-rc$NEXT
> > or shall
> > we wait until 4.3? I'm assuming this should go via the DT tree, but
> > maybe
> > it should go via an ARM tree?
>
> I was assuming this would go thru the arm-soc tree which is why I
> acked it. It is getting a bit late for 4.2 at this point, but I guess
> the standalone tree remains broken for these platforms until this is
> done.
Correct.
> Probably not such a big deal in grand scheme of things.
I guess not. FWIW I've not pushed since the breakage started happening,
so the split tree isn't broken, but it's also now however many weeks
behind. Once 4.3-rc1 arrives with this fixed I'll push all the 4.2-rcN
and 4.2 as well.
Ian.
next prev parent reply other threads:[~2015-08-16 9:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 16:06 [PATCH v5] dtb: Create a common home for cross-architecture dtsi files Ian Campbell
2015-08-03 16:06 ` Ian Campbell
2015-08-03 16:06 ` Ian Campbell
2015-08-03 16:06 ` Ian Campbell
2015-08-03 16:47 ` Frank Rowand
2015-08-03 16:47 ` Frank Rowand
2015-08-11 10:07 ` Ian Campbell
2015-08-11 10:07 ` Ian Campbell
2015-08-11 10:07 ` Ian Campbell
2015-08-14 21:21 ` Rob Herring
2015-08-14 21:21 ` Rob Herring
2015-08-16 9:01 ` Ian Campbell [this message]
2015-08-16 9:01 ` Ian Campbell
2015-08-23 23:13 ` Olof Johansson
2015-08-23 23:13 ` Olof Johansson
2015-08-23 23:42 ` Rob Herring
2015-08-23 23:42 ` Rob Herring
2015-08-23 23:52 ` Olof Johansson
2015-08-23 23:52 ` Olof Johansson
2015-08-24 20:58 ` Rob Herring
2015-08-24 20:58 ` Rob Herring
2015-08-24 20:58 ` Rob Herring
2015-08-24 22:22 ` Olof Johansson
2015-08-24 22:22 ` Olof Johansson
2015-08-24 22:22 ` Olof Johansson
2015-09-01 8:44 ` Ian Campbell
2015-09-01 8:44 ` Ian Campbell
2015-09-17 11:07 ` Ian Campbell
2015-09-17 11:07 ` Ian Campbell
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=1439715671.3480.21.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=arm@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=khilman@linaro.org \
--cc=kristina.martsenko@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.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 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.