From: Scott Wood <oss@buserror.net>
To: Alessio Igor Bogani <alessio.bogani@elettra.eu>,
Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: mpc8641si-pre.dtsi and mpc8641si-post.dtsi
Date: Wed, 10 Feb 2016 16:03:03 -0600 [thread overview]
Message-ID: <1455141783.2463.9.camel@buserror.net> (raw)
In-Reply-To: <CAPk1OjEAMaZjup2UWmtibyDtM1qSH7OuKQqgLV4iDnBm5gF_8g@mail.gmail.com>
On Wed, 2016-02-10 at 15:40 +0100, Alessio Igor Bogani wrote:
> Hi Kumar, Scott and all,
>
> I'm wondering if actual make sense create files in subject to
> consolidate five device tree (gef_ppc9a.dts, gef_sbc310.dts,
> gef_sbc610.dts, mpc8641_hpcn.dts and sbc8641d.dts). If it makes sense
> what device tree can I take as example?
>
> Thank you very much!
Yes, and you can use the various 85xx/QorIQ trees as an example. FWIW, it
should be possible to move the pre content into post, and have only one dtsi.
-Scott
prev parent reply other threads:[~2016-02-10 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 14:40 mpc8641si-pre.dtsi and mpc8641si-post.dtsi Alessio Igor Bogani
2016-02-10 22:03 ` Scott Wood [this message]
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=1455141783.2463.9.camel@buserror.net \
--to=oss@buserror.net \
--cc=alessio.bogani@elettra.eu \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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).