public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] OneNAND: Add support	for	auto-placementofout-of-banddata
Date: Thu, 01 Feb 2007 10:02:03 +0200	[thread overview]
Message-ID: <45C19E7B.9060006@nokia.com> (raw)
In-Reply-To: <45C19A1F.4020201@nokia.com>

ext Adrian Hunter wrote:
> ext Kyungmin Park wrote:
>>> +	writeend = mtd->oobsize;
>> We don't re-assign the 'writeend'. It cause the block is not clean. Since
>> JFFS2 send only 12 bytes but onenand writes until oobsize, actually 20
>> bytes with zero.
>> So this statement will be removed.
> 
> Yes, that was a typo.  The line should have been deleted when the previous
> line was deleted.

The statement still seems to be in the onenand tree.  Here is a patch to remove it.


>From 397419987d744ed971c74cfabae2eeac705f2fe0 Mon Sep 17 00:00:00 2001
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
Date: Thu, 1 Feb 2007 09:59:41 +0200
Subject: [MTD] OneNAND: Remove line of code that was meant to be deleted

Iterations of the patch to add oob auto-placement support to
OneNAND left a line of code that was meant to have been deleted.

Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
---
 drivers/mtd/onenand/onenand_base.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/drivers/mtd/onenand/onenand_base.c b/drivers/mtd/onenand/onenand_base.c
index 67efbc7..9ec28bb 100644
--- a/drivers/mtd/onenand/onenand_base.c
+++ b/drivers/mtd/onenand/onenand_base.c
@@ -1143,7 +1143,6 @@ static int onenand_fill_auto_oob(struct 
 			writeend += free->offset - lastgap;
 		lastgap = free->offset + free->length;
 	}
-	writeend = mtd->oobsize;
 	for (free = this->ecclayout->oobfree; free->length; ++free) {
 		int free_end = free->offset + free->length;
 		if (free->offset < writeend && free_end > writecol) {
-- 
1.4.3

  reply	other threads:[~2007-02-01  8:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 15:13 [PATCH] [MTD] OneNAND: Add support for auto-placement of out-of-band data Adrian Hunter
2007-01-26 15:44 ` Adrian Hunter
2007-01-29  6:02   ` [PATCH] [MTD] OneNAND: Add support for auto-placement ofout-of-band data Kyungmin Park
2007-01-29  8:13     ` Adrian Hunter
2007-01-29 15:36       ` Adrian Hunter
2007-01-30  6:08         ` [PATCH] [MTD] OneNAND: Add support for auto-placementofout-of-band data Kyungmin Park
2007-01-31  8:45           ` Adrian Hunter
2007-01-31 15:42           ` Adrian Hunter
2007-02-01  2:26             ` [PATCH] [MTD] OneNAND: Add support for auto-placementofout-of-banddata Kyungmin Park
2007-02-01  7:43               ` Adrian Hunter
2007-02-01  8:02                 ` Adrian Hunter [this message]
2007-02-01  8:50                   ` [PATCH] [MTD] OneNAND: Add support forauto-placementofout-of-banddata Kyungmin Park
2007-02-01  9:39                     ` Adrian Hunter
2007-02-01  3:13             ` [PATCH] [MTD] OneNAND: Add support for auto-placementofout-of-banddata Kyungmin Park
2007-01-29 15:37       ` [PATCH] [MTD] OneNAND: Add support for auto-placement ofout-of-band data Adrian Hunter

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=45C19E7B.9060006@nokia.com \
    --to=ext-adrian.hunter@nokia.com \
    --cc=linux-mtd@lists.infradead.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