linux-kernel - Re: common location for devicetree files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131108165255.GA32668@titan.lakedaemon.net>
Date:	Fri, 8 Nov 2013 11:52:55 -0500
From:	Jason Cooper <jason@...edaemon.net>
To:	Kumar Gala <galak@...eaurora.org>
Cc:	devicetree@...r.kernel.org,
	"linux-kernel@...r.kernel.org list" <linux-kernel@...r.kernel.org>
Subject: Re: common location for devicetree files

On Thu, Nov 07, 2013 at 05:21:58PM -0600, Kumar Gala 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.

What do we really need to do before the move?  Should all arch dts files
be able to #include from any arch?  What's the minimum churn needed to
accomplish that?  Maybe just move the needed bits to arch/dts/include/ ?

I'm not real keen on separating by vendor.  For example, us mvebu folks
would probably miss useful/duplicated effort in another vendor's
subdirectory.  Which was the whole reason for moving driver code out of
machine directories to begin with.

thx,

Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/