From: Jason Cooper <jason@lakedaemon.net>
To: Olof Johansson <olof@lixom.net>
Cc: Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org list"
<linux-kernel@vger.kernel.org>
Subject: Re: common location for devicetree files
Date: Fri, 8 Nov 2013 14:37:22 -0500 [thread overview]
Message-ID: <20131108193722.GK10335@titan.lakedaemon.net> (raw)
In-Reply-To: <CAOesGMgyqXS8tq0Ru=ibypV89-oAJ8bzxhdFTnSAvfOobEC+Lw@mail.gmail.com>
On Fri, Nov 08, 2013 at 11:33:00AM -0800, Olof Johansson wrote:
> On Thu, Nov 7, 2013 at 3:21 PM, Kumar Gala <galak@codeaurora.org> wrote:
> > As we start having more sharing of device trees between architectures (arm & arm64, arm & powerpc, guessing maybe mips & arm) we need dts to live in location that
> >
> > I was wondering what people felt about doing:
> >
> > arch/dts/<VENDOR>/
> >
> > as a common location that could be shared. I'm up for other suggestions.
>
> dts isn't an architecture, so having it directly under arch/ doesn't
> make sense. I know it's the first common parent of a lot of platforms
> though.
>
> I'd be ok with adding a toplevel dts/ directory for this, for lack of
> better options. It doesn't really fit under firmware, lib, kernel,
> scripts, tools...
I'll admit I shied away from that thought (dts/) for fear of the wrath
of the greybeards. :)
thx,
Jason.
prev parent reply other threads:[~2013-11-08 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 23:21 Kumar Gala
2013-11-08 16:52 ` Jason Cooper
2013-11-08 17:59 ` Kumar Gala
2013-11-08 18:13 ` Jason Cooper
2013-11-08 18:17 ` Kumar Gala
2013-11-08 18:32 ` Jason Cooper
2013-11-11 16:24 ` Stephen Warren
2013-11-11 16:34 ` Jason Cooper
2013-11-11 17:35 ` Mark Rutland
2013-11-08 19:33 ` Olof Johansson
2013-11-08 19:37 ` Jason Cooper [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=20131108193722.GK10335@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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
all inboxes | Powered by JetHome®