From: Artem Bityutskiy <dedekind1@gmail.com>
To: Huang Shijie <b32955@freescale.com>
Cc: linux-mips@linux-mips.org, linus.walleij@linaro.org,
wim@iguana.be, paulus@samba.org, balbi@ti.com, mingo@kernel.org,
kgene.kim@samsung.com, linux@arm.linux.org.uk,
FlorianSchandinat@gmx.de, robert.richter@amd.com,
lliubbo@gmail.com, vapier@gentoo.org, a.p.zijlstra@chello.nl,
arnd@arndb.de, uclinux-dist-devel@blackfin.uclinux.org,
linux-arm-kernel@lists.infradead.org,
scott.jiang.linux@gmail.com, linux-kernel@vger.kernel.org,
ralf@linux-mips.org, linux-mtd@lists.infradead.org,
akpm@linux-foundation.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] kconfig: remove CONFIG_MTD_NAND_VERIFY_WRITE
Date: Fri, 24 Aug 2012 17:23:50 +0300 [thread overview]
Message-ID: <1345818230.2848.315.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1345021930-5033-1-git-send-email-b32955@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On Wed, 2012-08-15 at 17:12 +0800, Huang Shijie wrote:
> Just as Artem suggested:
>
> "Both UBI and JFFS2 are able to read verify what they wrote already.
> There are also MTD tests which do this verification. So I think there
> is no reason to keep this in the NAND layer, let alone wasting RAM in
> the driver to support this feature."
>
> So kill MTD_NAND_VERIFY_WRITE entirely. Please see the patch:
> http://lists.infradead.org/pipermail/linux-mtd/2012-August/043189.html
>
> This patch removes the CONFIG_MTD_NAND_VERIFY_WRITE in the defconfigs.
>
>
> Signed-off-by: Huang Shijie <b32955@freescale.com>
Pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-08-24 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 9:12 [PATCH] kconfig: remove CONFIG_MTD_NAND_VERIFY_WRITE Huang Shijie
2012-08-24 14:23 ` 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=1345818230.2848.315.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=FlorianSchandinat@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=b32955@freescale.com \
--cc=balbi@ti.com \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lliubbo@gmail.com \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=robert.richter@amd.com \
--cc=scott.jiang.linux@gmail.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
--cc=wim@iguana.be \
/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).