From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Poonam Aggrwal <poonam.aggrwal@freescale.com>,
linuxppc-dev@lists.ozlabs.org, linux-mtd@lists.infradead.org,
Prabhakar Kushwaha <prabhakar@freescale.com>
Subject: Re: [PATCH 2/2][v2] mtd/nand: Fix IFC driver to support 2K NAND page
Date: Tue, 17 Jan 2012 13:10:00 -0600 [thread overview]
Message-ID: <4F15C788.2050701@freescale.com> (raw)
In-Reply-To: <C8C27406-1682-4316-97D1-00EFB5898805@kernel.crashing.org>
On 01/17/2012 12:57 PM, Kumar Gala wrote:
>
> On Jan 9, 2012, at 7:10 PM, Scott Wood wrote:
>
>> On 01/09/2012 06:24 AM, Prabhakar Kushwaha wrote:
>>> 1) OOB area should be updated irrespective of NAND page size. Earlier it was
>>> updated only for 512byte NAND page.
>>>
>>> 2) During OOB update fbcr should be equal to OOB size.
>>>
>>> Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
>>> Signed-off-by: Prabhakar Kushwaha <prabhakar@freescale.com>
>>> ---
>>> git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git (branch next)
>>>
>>> This patch is created on top of IFC driver patch (already floated in mailing
>>> list). Please find their link:
>>> http://patchwork.ozlabs.org/patch/133315/
>>> http://patchwork.ozlabs.org/patch/133316/
>>
>> Looks good.
>>
>> -Scott
>
> Can we not merge all these into one updated IFC NAND patch?
Sure, once we've agreed on what the right fix is for the is_blank issue
(and I think we're pretty close). It's been useful to see these fixes
as separate patches during the review/iteration phase, though.
-Scott
prev parent reply other threads:[~2012-01-17 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 12:24 [PATCH 2/2][v2] mtd/nand: Fix IFC driver to support 2K NAND page Prabhakar Kushwaha
2012-01-10 1:10 ` Scott Wood
2012-01-17 18:57 ` Kumar Gala
2012-01-17 18:57 ` Kumar Gala
2012-01-17 19:10 ` Scott Wood [this message]
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=4F15C788.2050701@freescale.com \
--to=scottwood@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=poonam.aggrwal@freescale.com \
--cc=prabhakar@freescale.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.