From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: "Stanley.Miao" <stanley.miao@windriver.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Fix mtd-utils bugs
Date: Sun, 13 Jun 2010 12:51:58 +0300 [thread overview]
Message-ID: <1276422718.19028.211.camel@localhost> (raw)
In-Reply-To: <1276248975-1822-1-git-send-email-stanley.miao@windriver.com>
On Fri, 2010-06-11 at 17:36 +0800, Stanley.Miao wrote:
> Re-send them because I didn't give a email subject in last version.
>
> The "struct nand_oobinfo" is able to record only 32 ECC code positions,which
> is not enough for many big NAND chips. Therefore, this structure is replaced
> by "struct nand_ecclayout" in linux kernel from the version 2.6.17.
> Consequently, the ioctl command changed from MEMGETOOBSEL to ECCGETLAYOUT.
>
> Now update nandwrite to use the new ioctl command ECCGETLAYOUT. In order to
> keep compatible with the old linux kernel, a linux version detection function
> is added.
>
> YAFFS and JFFS2 has updated and we don't need the arguments "forcelegacy",
> "forcejffs2", "forceyaffs" anymore. Now clean them up.
Please, make sure your submissions have proper version. I have limited
amount of time and do not want to spend it figuring out which patch is
the latest. Use the best kernel practices and apply prefix your stuff
with [PATCHv3] or something like that.
Could you please re-submit your latest version?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-06-13 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 9:36 Fix mtd-utils bugs Stanley.Miao
2010-06-11 9:36 ` [PATCH 1/3] clean up the legacy interfaces in nandwrite.c Stanley.Miao
2010-06-11 9:36 ` [PATCH 2/3] Discard the legacy interface MEMGETOOBSEL in flash_eraseall Stanley.Miao
2010-06-11 9:36 ` [PATCH 3/3] Place the cleanmarker in OOB area according to the mode MTD_OOB_AUTO Stanley.Miao
2010-06-11 9:44 ` [PATCH 2/3] Discard the legacy interface MEMGETOOBSEL in flash_eraseall Joakim Tjernlund
[not found] ` <OFDBEF7A42.BA0205E8-ONC125773F.0034F62C-C125773F.00358229@LocalDomain>
2010-06-11 9:53 ` Joakim Tjernlund
2010-06-11 10:36 ` stanley.miao
2010-06-11 10:44 ` Joakim Tjernlund
2010-06-11 12:11 ` Joakim Tjernlund
2010-06-13 9:51 ` Artem Bityutskiy [this message]
2010-06-13 10:14 ` Fix mtd-utils bugs Artem Bityutskiy
2010-06-17 4:10 ` stanley.miao
2010-06-18 8:16 ` stanley.miao
2010-06-18 10:24 ` Artem Bityutskiy
2010-06-20 12:21 ` stanley.miao
-- strict thread matches above, loose matches on Subject: below --
2010-02-03 4:45 Stanley.Miao
2010-02-04 7:25 ` stanley.miao
2010-02-15 13:36 ` 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=1276422718.19028.211.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stanley.miao@windriver.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).