From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: MTD Maling List <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 5/8] mtd: docg3: initialize writebufsize
Date: Fri, 03 Feb 2012 16:44:25 +0100 [thread overview]
Message-ID: <87ipjn53c6.fsf@free.fr> (raw)
In-Reply-To: <31119f54134de4f631ae48a6941d773450000e98.1328257053.git.artem.bityutskiy@linux.intel.com> (Artem Bityutskiy's message of "Fri, 3 Feb 2012 10:43:11 +0200")
Artem Bityutskiy <dedekind1@gmail.com> writes:
> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>
> The writebufsize concept was introduce by commit
> "0e4ca7e mtd: add writebufsize field to mtd_info struct" and it represents
> the maximum amount of data the device writes to the media at a time. This is
> an important parameter for UBIFS which is used during recovery and which
> basically defines how big a corruption caused by a power cut can be.
>
> Set it to be equivalent to mtd->writesize because this is the maximum amount
> of data the driver writes at a time.
Acked-by: Robert Jarzmik <robert.jarzmik@free.fr>
--
Robert
next prev parent reply other threads:[~2012-02-03 15:44 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 [this message]
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
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=87ipjn53c6.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=dedekind1@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.