From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: MTD Maling List <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 1/8] mtd: block2mtd: initialize writebufsize
Date: Mon, 06 Feb 2012 11:07:56 +0200 [thread overview]
Message-ID: <1328519276.22240.27.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120204180035.GB28736@logfs.org>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
On Sat, 2012-02-04 at 13:00 -0500, Jörn Engel wrote:
> > Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> > Cc: stable@kernel.org [2.6.38+]
> > Cc: Joern Engel <joern@lazybastard.org>
>
> Acked-by: Joern Engel <joern@lazybastard.org>
Added, thanks!
> From the description of 0e4ca7e it appears as if using a minimum of
> say 8 for ubifs recovery would have done the trick as well. Oh well!
It actually need to know the maximum size of the corrupted area. In case
of block2mtd in theory, the whole 512 bytes may be corrupted, even
though I update 1 byte. For real CFI NORs - it is 16 bytes AFAIR.
--
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-02-06 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 8:43 [PATCH 1/8] mtd: block2mtd: initialize writebufsize Artem Bityutskiy
2012-02-03 8:43 ` [PATCH 2/8] mtd: doc2000: " Artem Bityutskiy
2012-02-03 8:43 ` [PATCH 3/8] mtd: doc2001: " Artem Bityutskiy
2012-02-03 8:43 ` [PATCH 4/8] mtd: doc2001plus: " Artem Bityutskiy
2012-02-03 8:43 ` [PATCH 5/8] mtd: docg3: " Artem Bityutskiy
2012-02-03 15:44 ` Robert Jarzmik
2012-02-03 8:43 ` [PATCH 6/8] mtd: lart: " Artem Bityutskiy
2012-02-03 8:43 ` [PATCH 7/8] mtd: spear_smi: " Artem Bityutskiy
2012-02-03 8:45 ` Stefan Roese
2012-02-03 8:43 ` [PATCH 8/8] mtd: sst25l: " Artem Bityutskiy
2012-02-04 18:00 ` [PATCH 1/8] mtd: block2mtd: " Jörn Engel
2012-02-06 9:07 ` 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=1328519276.22240.27.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.org \
/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