From: Sekhar Nori <nsekhar@ti.com>
To: "ivan.khoronzhuk" <ivan.khoronzhuk@ti.com>, <dwmw2@infradead.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
grygorii.strashko@ti.com, linux@arm.linux.org.uk,
pawel.moll@arm.com, swarren@wwwdotorg.org,
ijc+devicetree@hellion.org.uk, galak@kernel.crashing.org,
rob.herring@calxeda.com, linux-kernel@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
rob@landley.net, linux-mtd@lists.infradead.org,
computersforpeace@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif
Date: Wed, 18 Dec 2013 17:43:14 +0530 [thread overview]
Message-ID: <52B1915A.7060309@ti.com> (raw)
In-Reply-To: <52B18C44.2000305@ti.com>
On Wednesday 18 December 2013 05:21 PM, ivan.khoronzhuk wrote:
> Hi, Sekhar
>
> This patch is based on "Reuse davinci-nand driver for Keystone arch" series.
> The series has passed review at https://lkml.org/lkml/2013/12/17/241
> and can be found at http://git.infradead.org/l2-mtd.git
>
> This patch can be still applied on top of the series without conflicts.
>
> Can you please pick up the $subject patch if you are OK with it?
I have no problems with the patch and can pick it too, but need ack from
MTD maintainer (David) as it touches drivers/mtd/ too.
David,
If you do not have the patch, we can resend it.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-12-18 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 18:11 [PATCH v3] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif Ivan Khoronzhuk
2013-12-06 21:04 ` Sekhar Nori
2013-12-09 8:58 ` ivan.khoronzhuk
2013-12-18 11:51 ` ivan.khoronzhuk
2013-12-18 12:13 ` Sekhar Nori [this message]
2013-12-26 12:06 ` ivan.khoronzhuk
2014-01-09 10:39 ` Sekhar Nori
2014-01-09 16:33 ` Brian Norris
2014-01-10 4:19 ` Sekhar Nori
2014-01-10 7:15 ` Sekhar Nori
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=52B1915A.7060309@ti.com \
--to=nsekhar@ti.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@kernel.crashing.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=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=santosh.shilimkar@ti.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;
as well as URLs for NNTP newsgroup(s).