From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Stanley.Miao" <stanley.miao@windriver.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [v3 1/3] clean up the legacy interfaces in nandwrite.c
Date: Sat, 18 Sep 2010 20:20:40 +0300 [thread overview]
Message-ID: <1284830440.1721.2.camel@brekeke> (raw)
In-Reply-To: <1276857173-10848-2-git-send-email-stanley.miao@windriver.com>
On Fri, 2010-06-18 at 18:32 +0800, Stanley.Miao wrote:
> 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.
>
> Signed-off-by: Stanley.Miao <stanley.miao@windriver.com>
I still have this series marked with red in my box, which means "do not
forget about this". But since this stuff is so old and you disappeared,
I am unmarking this.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2010-09-18 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 10:32 [PATCH v3] Fix mtd-utils bugs Stanley.Miao
2010-06-18 10:20 ` [v3 1/3] clean up the legacy interfaces in nandwrite.c Stanley.Miao
2010-06-18 10:20 ` [v3 2/3] Discard the legacy interface MEMGETOOBSEL in flash_eraseall Stanley.Miao
2010-06-18 10:20 ` [v3 3/3] Place the cleanmarker in OOB area according to the mode MTD_OOB_AUTO Stanley.Miao
2010-09-18 17:20 ` Artem Bityutskiy [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=1284830440.1721.2.camel@brekeke \
--to=dedekind1@gmail.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).