From: Artem Bityutskiy <dedekind@infradead.org>
To: vimal singh <vimalsingh@ti.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-mtd@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [resending-2] [PATCH] [MTD] [NAND] Add OMAP2 / OMAP3 NAND driver
Date: Tue, 02 Jun 2009 16:48:00 +0300 [thread overview]
Message-ID: <1243950480.5847.35.camel@localhost.localdomain> (raw)
In-Reply-To: <52785.192.168.10.89.1243833774.squirrel@dbdmail.itg.ti.com>
On Mon, 2009-06-01 at 10:52 +0530, vimal singh wrote:
> On Fri, May 15, 2009 at 6:38 PM, Artem Bityutskiy <dedekind@infradead.org> wrote:
> > On Thu, 2009-04-30 at 15:03 +0530, vimal singh wrote:
> >> This driver is present in the OMAP tree, now pushing it to MTD.
> >>
> >> Original author(s):
> >> Jian Zhang <jzhang@ti.com>
> >>
> >> Signed-off-by: Vimal Singh <vimalsingh@ti.com>
> >> ---
> >> drivers/mtd/nand/Kconfig | 6
> >> drivers/mtd/nand/Makefile | 1
> >> drivers/mtd/nand/omap2.c | 776
> ++++++++++++++++++++++++++++++++++++++++++++++
> >> 3 files changed, 783 insertions(+)
> >
> > Hi Thomas,
> >
> > would you please find a little time and Ack/Nack this
> > please?
>
> Artem,
> This patch is still pending. This patch has already been reviewed by you and
> Andrew Morton. Seems like Thomas is not finding time to review this. What
> should be the next step about this?
Unfortunately, I do not think I'm able to really review your driver.
So all I can do for you is to put your driver to my l2-mtd-2.6.git
tree into the "dunno" branch, and let dwmw2 review it. Which I did.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-06-02 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 5:22 [resending-2] [PATCH] [MTD] [NAND] Add OMAP2 / OMAP3 NAND driver vimal singh
2009-06-02 13:48 ` Artem Bityutskiy [this message]
[not found] <61255.192.168.10.89.1240984646.squirrel@dbdmail.itg.ti.com>
2009-04-30 9:33 ` vimal singh
2009-05-15 13:08 ` Artem Bityutskiy
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=1243950480.5847.35.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
--cc=vimalsingh@ti.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).