From: Roger Quadros <rogerq@ti.com>
To: <tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>, <fcooper@ti.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] ARM: dts: omap2+: GPMC NAND node fixes (part 2)
Date: Tue, 1 Mar 2016 15:50:11 +0200 [thread overview]
Message-ID: <56D59E13.4060502@ti.com> (raw)
In-Reply-To: <1456839888-6244-1-git-send-email-rogerq@ti.com>
On 01/03/16 15:44, Roger Quadros wrote:
> Hi Tony,
>
> These patches are a preparatory step towards the NAND DT cleanup
> done in [1].
>
> They mostly deal with adding the missing compatible property and
> interrupt resources and fixing up register resources for the
> NAND nodes for the boards that add NAND support in v4.6.
>
> Patches based on tony/omap-for-v4.6/dt
[1] - http://article.gmane.org/gmane.linux.kernel/2156857
cheers,
-roger
next prev parent reply other threads:[~2016-03-01 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 13:44 [PATCH 0/2] ARM: dts: omap2+: GPMC NAND node fixes (part 2) Roger Quadros
2016-03-01 13:44 ` [PATCH 1/2] ARM: dts: dm814x: dra62x: Fix NAND device nodes Roger Quadros
2016-03-01 13:44 ` [PATCH 2/2] ARM: dts: dm814x: dra62x: Disable wait pin monitoring for NAND Roger Quadros
2016-03-01 13:50 ` Roger Quadros [this message]
2016-03-01 18:01 ` [PATCH 0/2] ARM: dts: omap2+: GPMC NAND node fixes (part 2) Tony Lindgren
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=56D59E13.4060502@ti.com \
--to=rogerq@ti.com \
--cc=fcooper@ti.com \
--cc=linux-kernel@vger.kernel.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).