From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org list"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: common location for devicetree files
Date: Mon, 11 Nov 2013 09:24:13 -0700 [thread overview]
Message-ID: <528104AD.9030102@wwwdotorg.org> (raw)
In-Reply-To: <20131108183240.GH10335-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
On 11/08/2013 11:32 AM, Jason Cooper wrote:
> On Fri, Nov 08, 2013 at 12:17:30PM -0600, Kumar Gala wrote:
> ...
>> I get the point, just not sure how else to sort the 800+ .dts{i} files
>> that we have in the kernel tree right now.
>
> Well, to start with, all #include'd files could go into a
> arch/dts/include directory. That would clean things up a bit.
>
> We could also consider separating the dts files by ISA. All armv7 in
> one directory, armv8, armv5te, powerpc, mips, etc.
It's quite likely people will want to share some significant *.dtsi
across multiple architectures.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-11 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 23:21 common location for devicetree files Kumar Gala
2013-11-08 16:52 ` Jason Cooper
[not found] ` <20131108165255.GA32668-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
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
[not found] ` <20131108183240.GH10335-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2013-11-11 16:24 ` Stephen Warren [this message]
[not found] ` <528104AD.9030102-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-11 16:34 ` Jason Cooper
2013-11-11 17:35 ` Mark Rutland
[not found] ` <1438803E-C904-428B-B042-891978BC15DF-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-11-08 19:33 ` Olof Johansson
2013-11-08 19:37 ` Jason Cooper
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=528104AD.9030102@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).