From: Ian Campbell <ian.campbell@citrix.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Sudeep Holla <Sudeep.Holla@arm.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Russell King <linux@arm.linux.org.uk>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
Kristina Martsenko <Kristina.Martsenko@arm.com>,
Kevin Hilman <khilman@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] dtb: Create a common home for cross-architecture dtsi files.
Date: Wed, 22 Jul 2015 10:47:18 +0100 [thread overview]
Message-ID: <1437558438.8383.72.camel@citrix.com> (raw)
In-Reply-To: <20150722084753.GC14923@e106497-lin.cambridge.arm.com>
On Wed, 2015-07-22 at 09:47 +0100, Liviu Dudau wrote:
>
> Acked-by: Liviu Dudau <Liviu.Dudau@arm.com>
Thanks.
> Picking your brains here: would it be worth to have some vendor directories in
> this shared area or we can hope that there will be very few files living here?
I'm honestly not sure.
I don't expect there will be very many files under here, and I would
expect the norm would be that common .dtsi files used by multiple
arches would be things from the same vendor, but I don't think we can
guarantee that.
Ian.
next prev parent reply other threads:[~2015-07-22 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 16:30 [PATCH] dtb: Create a common home for cross-architecture dtsi files Ian Campbell
2015-07-22 8:47 ` Liviu Dudau
2015-07-22 9:47 ` Ian Campbell [this message]
[not found] ` <1437558438.8383.72.camel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2015-07-24 11:31 ` Mark Rutland
2015-07-24 11:39 ` 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=1437558438.8383.72.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Catalin.Marinas@arm.com \
--cc=Kristina.Martsenko@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=Will.Deacon@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robh+dt@kernel.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).