From: Sekhar Nori <nsekhar@ti.com>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: Rob Herring <robherring2@gmail.com>,
dwmw2@infradead.org, artem.bityutskiy@linux.intel.com,
b32955@freescale.com, shubhrajyoti@ti.com, wim@iguana.be,
hs@denx.de, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
rob@landley.net, gregkh@linuxfoundation.org,
swarren@wwwdotorg.org, hdoyu@nvidia.com,
santosh.shilimkar@ti.com, devicetree-discuss@lists.ozlabs.org,
linux-doc@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [RFC PATCH 1/2] memory: davinci - add aemif controller platform driver
Date: Tue, 6 Nov 2012 13:14:33 +0530 [thread overview]
Message-ID: <5098BFE1.3020906@ti.com> (raw)
In-Reply-To: <50982AC3.8030000@ti.com>
On 11/6/2012 2:38 AM, Murali Karicheri wrote:
> On 11/04/2012 08:52 AM, Rob Herring wrote:
>> OMAP GPMC
> Could you send me a link please?
https://www.google.com/search?q=RFC+OMAP+GPMC+DT+bindings
The patches series is sent by Daniel Mack. v3 was the last version sent.
Thanks,
Sekhar
next prev parent reply other threads:[~2012-11-06 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 16:21 [RFC PATCH 0/2] - Move AEMIF driver out of DaVinci machine Murali Karicheri
2012-11-02 16:21 ` [RFC PATCH 1/2] memory: davinci - add aemif controller platform driver Murali Karicheri
2012-11-02 19:05 ` Stephen Warren
2012-11-06 18:30 ` Murali Karicheri
2012-11-04 13:52 ` Rob Herring
2012-11-05 21:08 ` Murali Karicheri
2012-11-06 7:44 ` Sekhar Nori [this message]
2012-11-06 16:04 ` Murali Karicheri
2012-11-06 16:42 ` Murali Karicheri
[not found] ` <1351873278-27325-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2012-11-02 16:21 ` [RFC PATCH 2/2] mtd: davinci - remove DaVinci architecture depedency Murali Karicheri
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=5098BFE1.3020906@ti.com \
--to=nsekhar@ti.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=hdoyu@nvidia.com \
--cc=hs@denx.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=m-karicheri2@ti.com \
--cc=rob@landley.net \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.com \
--cc=shubhrajyoti@ti.com \
--cc=swarren@wwwdotorg.org \
--cc=wim@iguana.be \
/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).