From: Artem Bityutskiy <dedekind1@gmail.com>
To: Vimal Singh <vimal.newwork@gmail.com>
Cc: kishorek.kadiyala@gmail.com, Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v3 2/2] Adding nand lock/unlock routines.
Date: Tue, 16 Feb 2010 10:18:11 +0200 [thread overview]
Message-ID: <1266308291.11659.179.camel@localhost> (raw)
In-Reply-To: <ce9ab5791002150650x79e40747w7aa345c115356d06@mail.gmail.com>
On Mon, 2010-02-15 at 20:20 +0530, Vimal Singh wrote:
> On Mon, Feb 15, 2010 at 8:05 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Mon, 2010-02-08 at 15:50 +0530, Vimal Singh wrote:
> >> This version fixes the compilation break reported by Kishore. 1st
> >> patch in this series remains untouched.
> >>
> >> -vimal
> >>
> >> From a28c230f3bd8fa765f78c0be91370f146e71f670 Mon Sep 17 00:00:00 2001
> >> From: Vimal Singh <vimalsingh@ti.com>
> >> Date: Wed, 3 Feb 2010 14:32:06 +0530
> >> Subject: [PATCH 2/2] Adding nand lock/unlock routines.
> >>
> >> Adding nand lock / unlock routines. At least 'micron' parts
> >> support this.
> >>
> >> Signed-off-by: Vimal Singh <vimalsingh@ti.com>
> >
> > These look OK to me, except the part where you export them. Why they
> > should be exported?
>
> There was an earlier comment (in 1st RFC version of the patch), where
> you said probably it is not safer to assign mtd lock and unlock
> pointers in 'nand_scan_tail', as not all flashes have this feature.
>
> So, I exported these so that a driver can use these by overwriting mtd
> lock and unlock pointers in its probe.
OK, push to my l2-mtd-2.6.git / master
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-02-16 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 10:20 [PATCH v3 2/2] Adding nand lock/unlock routines Vimal Singh
2010-02-15 14:35 ` Artem Bityutskiy
2010-02-15 14:50 ` Vimal Singh
2010-02-16 8:18 ` Artem Bityutskiy [this message]
2010-02-16 8:55 ` Vimal Singh
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=1266308291.11659.179.camel@localhost \
--to=dedekind1@gmail.com \
--cc=kishorek.kadiyala@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vimal.newwork@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.