devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: "Dmitry Lifshitz" <lifshitz@compulab.co.il>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: cm-t3x: add NAND support
Date: Sun, 28 Dec 2014 15:55:34 +0200	[thread overview]
Message-ID: <54A00BD6.8010507@compulab.co.il> (raw)
In-Reply-To: <1419772503-11671-1-git-send-email-lifshitz@compulab.co.il>

Hi Dima,

On 12/28/14 15:15, Dmitry Lifshitz wrote:
> Add NAND support
> 
> Signed-off-by: Dmitry Lifshitz <lifshitz@compulab.co.il>
> ---
>  arch/arm/boot/dts/omap3-cm-t3x.dtsi   |   58 +++++++++++++++++++++++++++++++++
>  arch/arm/boot/dts/omap3-sbc-t3517.dts |    4 ++
>  arch/arm/boot/dts/omap3-sbc-t3530.dts |   10 ++----
>  arch/arm/boot/dts/omap3-sbc-t3730.dts |    5 ++-
>  4 files changed, 68 insertions(+), 9 deletions(-)

It seems that you have missed the omap3-cm-t3x30.dtsi.
If after this patch you build omap3-cm-t3530.dts or omap3-cm-t3730.dts,
it will not have NAND, while they should get it as well.

-- 
Regards,
Igor.

  reply	other threads:[~2014-12-28 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28 13:15 [PATCH] ARM: dts: cm-t3x: add NAND support Dmitry Lifshitz
2014-12-28 13:55 ` Igor Grinberg [this message]
2014-12-28 14:30   ` [PATCH v2] " Dmitry Lifshitz
2014-12-28 14:54     ` Igor Grinberg
2014-12-29 13:06     ` Roger Quadros
2014-12-30  7:39       ` Dmitry Lifshitz
2015-01-08  0:16         ` Tony Lindgren
2015-01-08 10:30           ` Roger Quadros
2015-01-13 16:01             ` Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2014-12-28 11:37 [PATCH] " Dmitry Lifshitz

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=54A00BD6.8010507@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lifshitz@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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).