From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: <gregkh@linuxfoundation.org>
Cc: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>,
<galak@kernel.crashing.org>, <rob@landley.net>,
<robherring2@gmail.com>, <linux@arm.linux.org.uk>,
<devicetree@vger.kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <rob.herring@calxeda.com>,
<swarren@wwwdotorg.org>, <ijc+devicetree@hellion.org.uk>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mtd@lists.infradead.org>, <grygorii.strashko@ti.com>,
<dwmw2@infradead.org>, <nsekhar@ti.com>
Subject: Re: [PATCH v6 0/2] Introduce AEMIF driver for Davinci/Keystone archs
Date: Fri, 28 Feb 2014 10:43:36 -0500 [thread overview]
Message-ID: <5310AEA8.1070804@ti.com> (raw)
In-Reply-To: <1393262772-24442-1-git-send-email-ivan.khoronzhuk@ti.com>
Greg,
On Monday 24 February 2014 12:26 PM, Ivan Khoronzhuk wrote:
> These patches introduce Async External Memory Interface (EMIF16/AEMIF)
> controller driver for Davinci/Keystone archs.
>
> For more informations see documentation:
> Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
> OMAP-L138 - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
> Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
>
[..]
>
> v5..v6:
> - memory: ti-aemif: introduce AEMIF driver
> - memory: ti-aemif: add bindings for AEMIF driver
> changed opaque names for cs node properties
>
Can you please pick these two patches ?
Regards,
Santosh
next prev parent reply other threads:[~2014-02-28 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 17:26 [PATCH v6 0/2] Introduce AEMIF driver for Davinci/Keystone archs Ivan Khoronzhuk
2014-02-24 17:26 ` [PATCH v6 1/2] memory: ti-aemif: introduce AEMIF driver Ivan Khoronzhuk
2014-02-24 17:26 ` [PATCH v6 2/2] memory: ti-aemif: add bindings for " Ivan Khoronzhuk
2014-02-28 15:43 ` Santosh Shilimkar [this message]
2014-02-28 16:06 ` [PATCH v6 0/2] Introduce AEMIF driver for Davinci/Keystone archs Greg KH
2014-02-28 16:18 ` Santosh Shilimkar
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=5310AEA8.1070804@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=robherring2@gmail.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