mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "stanley.miao" <stanley.miao@windriver.com>,
	Vitaly Wool <vitalywool@gmail.com>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: NAND: fixes
Date: Sat,  6 Feb 2010 01:18:03 +0200	[thread overview]
Message-ID: <1265411890-9156-1-git-send-email-maximlevitsky@gmail.com> (raw)

This is part of my patcheset that touches the nand subsystem

Stanley, patch #2 should now cover attempts to write outside the oob.

Also I did another (don't know if less or more evil) approach to bad block testing.
Now check_bad always takes the controller locks and selects the chip. Thus it is
possible to use read_oob/write_oob.
This however changes behavier of the nand_erase_nand to deny erases if any block within
the range is bad. Also it selects/releases the chip once per erase block.
This is done in patch #5. Patch #6 is ported to that change.

Patches 1-3 are pure fixes.

Best regards,
	Maxim Levitsky


             reply	other threads:[~2010-02-05 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 23:18 Maxim Levitsky [this message]
2010-02-05 23:18 ` [PATCH 1/7] MTD: nand: make MTD_OOB_PLACE work correctly Maxim Levitsky
2010-02-05 23:18 ` [PATCH 2/7] MTD: nand: cleanup nand_do_write_ops Maxim Levitsky
2010-02-05 23:18 ` [PATCH 3/7] MTD: nand: make suspend work if device is accessed by kernel threads Maxim Levitsky
2010-02-05 23:18 ` [PATCH 4/7] MTD: nand: make reads using MTD_OOB_RAW affect only ECC validation Maxim Levitsky
2010-02-05 23:18 ` [PATCH 5/7] NAND: make ->check_bad more user friendly Maxim Levitsky
2010-02-05 23:18 ` [PATCH 6/7] MTD: common module for smartmedia/xD support Maxim Levitsky
2010-02-05 23:18 ` [PATCH 7/7] MTD: add few workarounds to nand system for SmartMedia/xD chips Maxim Levitsky
2010-02-08 17:41 ` NAND: fixes Maxim Levitsky

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=1265411890-9156-1-git-send-email-maximlevitsky@gmail.com \
    --to=maximlevitsky@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=stanley.miao@windriver.com \
    --cc=vitalywool@gmail.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
all inboxes | Powered by JetHome®