From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix NAND erase progress error
Date: Fri, 16 May 2008 15:34:00 -0500 [thread overview]
Message-ID: <482DEFB8.6050704@freescale.com> (raw)
In-Reply-To: <42848A5C5A0D1E47B026E644DD49B08E026D1A23@mail>
Hugo Villeneuve wrote:
> I would be perfectly happy if the mtd driver reported a warning when the
> requested erase size is not an exact multiple of the block size, and
> allow the whole block erase to proceed. Then my patch would make sense.
That's what the mtd-2.6.22.1 branch in the NAND repository does. I
think it should reject such requests, though.
-Scott
next prev parent reply other threads:[~2008-05-16 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 18:39 [U-Boot-Users] [PATCH] Fix NAND erase progress error Hugo Villeneuve
2008-05-16 19:40 ` Scott Wood
2008-05-16 20:15 ` Hugo Villeneuve
2008-05-16 20:18 ` Scott Wood
2008-05-16 20:29 ` Hugo Villeneuve
2008-05-16 20:34 ` Scott Wood [this message]
2008-05-16 20:39 ` Hugo Villeneuve
2008-05-16 20:43 ` Scott Wood
2008-05-16 20:51 ` Hugo Villeneuve
2008-05-16 20:54 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2008-05-16 1:58 Hugo Villeneuve
2008-05-15 22:24 ` Wolfgang Denk
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=482DEFB8.6050704@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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