devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pawel Moll <pawel.moll@arm.com>
To: Grant Likely <grant.likely@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	Olof Johansson <olof@lixom.net>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership
Date: Mon, 22 Jul 2013 17:50:51 +0100	[thread overview]
Message-ID: <1374511851.3609.10.camel@hornet> (raw)
In-Reply-To: <1374290388-19308-3-git-send-email-grant.likely@linaro.org>

On Sat, 2013-07-20 at 04:19 +0100, Grant Likely wrote:
> +F:	include/dt-bindings

One thing we didn't finish talking about was the question if this
directory is supposed to contain *.dtsi files as well? The obvious
problem I have is a vexpress motherboard being (well, actually not bein
right now) shared between arch/arm/boot/dts and arch/arm64/boot/dts.

Pawel

  parent reply	other threads:[~2013-07-22 16:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1374290388-19308-1-git-send-email-grant.likely@linaro.org>
2013-07-20  3:19 ` [PATCH 2/3] MAINTAINERS: Change device tree mailing list Grant Likely
     [not found] ` <1374290388-19308-1-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-07-20  3:19   ` [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership Grant Likely
2013-07-20 16:20     ` Linus Walleij
     [not found]       ` <CACRpkdb2bPQOD2CBzbF0K33mZZwKwGSCO6B4djesVd5DR-Z1tA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-21 13:46         ` Jon Loeliger
     [not found]           ` <E1V0txk-0007v7-0J-CYoMK+44s/E@public.gmane.org>
2013-07-22  0:33             ` Grant Likely
2013-07-22  1:27           ` David Gibson
2013-07-22 17:38             ` Jon Loeliger
2013-07-21  0:17     ` Olof Johansson
2013-07-21  0:29       ` Joe Perches
2013-07-21  9:46         ` Grant Likely
2013-07-22  0:36           ` Grant Likely
2013-07-22 17:29           ` Olof Johansson
     [not found]     ` <1374290388-19308-3-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-07-21 18:56       ` Rob Herring
2013-07-22  0:35         ` Grant Likely
2013-07-22 20:31           ` Rob Herring
2013-07-22 21:36             ` Jon Loeliger
2013-07-23  3:27               ` Rob Herring
2013-07-22 16:50     ` Pawel Moll [this message]
2013-07-22 20:03       ` Rob Herring
2013-07-23 17:14         ` Pawel Moll
2013-07-23 17:59           ` Stephen Warren
2013-07-23 18:09             ` Ian Campbell
2013-07-23 18:44               ` Rob Herring
2013-07-23 18:55                 ` Ian Campbell
2013-07-23 19:28                   ` Rob Herring
2013-07-23 19:53                   ` Stephen Warren
2013-08-07 10:53                 ` Ian Campbell
2013-07-23 19:26             ` Nicolas Pitre

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=1374511851.3609.10.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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).