From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] dtb: Create a common home for cross-architecture dtsi files.
Date: Fri, 14 Aug 2015 16:21:51 -0500 [thread overview]
Message-ID: <CAL_JsqKv2aOEM-U7JNZnaHomA6HFBSFhSLZ-zhp7c20s6gQBaQ@mail.gmail.com> (raw)
In-Reply-To: <1439287646.9747.212.camel@citrix.com>
+arm-soc
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. Probably not such a big deal in grand scheme of things.
Rob
next prev parent reply other threads:[~2015-08-14 21:21 UTC|newest]
Thread overview: 12+ 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:47 ` Frank Rowand
2015-08-11 10:07 ` Ian Campbell
2015-08-14 21:21 ` Rob Herring [this message]
2015-08-16 9:01 ` Ian Campbell
2015-08-23 23:13 ` Olof Johansson
2015-08-23 23:42 ` Rob Herring
2015-08-23 23:52 ` Olof Johansson
2015-08-24 20:58 ` Rob Herring
2015-08-24 22:22 ` Olof Johansson
2015-09-01 8:44 ` 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=CAL_JsqKv2aOEM-U7JNZnaHomA6HFBSFhSLZ-zhp7c20s6gQBaQ@mail.gmail.com \
--to=robherring2@gmail.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).