devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pawel Moll <pawel.moll@arm.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	devicetree@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 1/2] video: ARM CLCD: Add DT support
Date: Mon, 23 Jun 2014 14:47:43 +0100	[thread overview]
Message-ID: <1403531263.3804.6.camel@hornet> (raw)
In-Reply-To: <53A809D4.90800@ti.com>

On Mon, 2014-06-23 at 14:04 +0300, Tomi Valkeinen wrote:
> I can queue this to fbdev tree, but how do you want to handle the second
> patch? I think these two patches are independent, so the second patch
> could go via arm-soc tree (or whichever is the normal route for those
> .dts file changes). I'd prefer that option.

That's exactly what I had on mind. I'll handle the dts changes when the
time is right.

Thanks!

Pawel

      reply	other threads:[~2014-06-23 13:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 15:21 [PATCH v7 1/2] video: ARM CLCD: Add DT support Pawel Moll
2014-06-17 15:21 ` [PATCH v7 2/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
     [not found] ` <1403018494-10264-1-git-send-email-pawel.moll-5wv7dgnIgG8@public.gmane.org>
2014-06-20 17:09   ` [PATCH v7 1/2] video: ARM CLCD: Add DT support Mark Rutland
2014-06-23 14:13     ` Pawel Moll
2014-06-23 14:55       ` [PATCH v8 " Pawel Moll
     [not found]         ` <1403535318-19333-1-git-send-email-pawel.moll-5wv7dgnIgG8@public.gmane.org>
2014-06-23 14:55           ` [PATCH v2 2/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
2014-06-23 15:43       ` [PATCH v7 1/2] video: ARM CLCD: Add DT support Rob Herring
     [not found]         ` <CAL_Jsq+6SveWhzWPrtziTJ-tDOFaJV4sXO+r_CEhAZf=tQE6FA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-23 15:59           ` Pawel Moll
2014-06-23 17:56             ` Rob Herring
     [not found]               ` <CAL_JsqLQTT5N8D_GTDd5YVgr2SSCXtC6EcRQxW2=_-J8Wmsf0g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-24 11:54                 ` Pawel Moll
2014-06-20 22:27   ` Peter Maydell
2014-06-23 13:52     ` Pawel Moll
2014-06-23 14:10       ` Russell King - ARM Linux
     [not found]         ` <20140623141022.GJ32514-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-06-23 14:23           ` Pawel Moll
2014-06-23 11:04   ` Tomi Valkeinen
2014-06-23 13:47     ` Pawel Moll [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=1403531263.3804.6.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /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).