From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: kmpark@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH/RFC] OneNAND simulator support
Date: Fri, 23 Mar 2007 09:57:59 +0200 [thread overview]
Message-ID: <46038887.6040301@nokia.com> (raw)
In-Reply-To: <00f801c76cdd$164a9fb0$c7a3580a@swcenter.sec.samsung.co.kr>
ext Kyungmin Park wrote:
> To Adrian,
>
> After patch http://git.infradead.org/?p=mtd-
> 2.6.git;a=commitdiff;h=5bc399e9ef430efd5725b66aa2ad7ad2d81e372b;hp=81280d5879761
> f90b3a341d52371d03998730d8e
>
> --- a/drivers/mtd/onenand/onenand_base.c
> +++ b/drivers/mtd/onenand/onenand_base.c
> @@ -854,7 +854,8 @@ static int onenand_transfer_auto_oob(str
> int n = ed - st;
> memcpy(buf, oob_buf + st, n);
> buf += n;
> - }
> + } else
> + break;
> }
> return 0;
> }
> @@ -1295,7 +1296,8 @@ static int onenand_fill_auto_oob(struct
> int n = ed - st;
> memcpy(oob_buf + st, buf, n);
> buf += n;
> - }
> + } else
> + break;
> }
> return 0;
> }
>
> It don't pass the oobtest since I assume oob passed at first, but oobtest don't
> do that.
> Basically I optimizeed it for JFFS2.
> Do I revert it or do nothing? please give your opinion.
How about this: (NB I haven't tried it but maybe it works ;-)
--- a/drivers/mtd/onenand/onenand_base.c
+++ b/drivers/mtd/onenand/onenand_base.c
@@ -854,7 +854,8 @@ static int onenand_transfer_auto_oob(str
int n = ed - st;
memcpy(buf, oob_buf + st, n);
buf += n;
- }
+ } else if (column == 0)
+ break;
}
return 0;
}
@@ -1295,7 +1296,8 @@ static int onenand_fill_auto_oob(struct
int n = ed - st;
memcpy(oob_buf + st, buf, n);
buf += n;
- }
+ } else if (column == 0)
+ break;
}
return 0;
}
next prev parent reply other threads:[~2007-03-23 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 0:51 [PATCH/RFC] OneNAND simulator support Kyungmin Park
2007-03-22 9:28 ` Artem Bityutskiy
2007-03-22 23:51 ` Kyungmin Park
2007-03-23 0:14 ` Kyungmin Park
2007-03-23 7:57 ` Adrian Hunter [this message]
2007-03-23 8:15 ` Kyungmin Park
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=46038887.6040301@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=kmpark@infradead.org \
--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