From: Artem Bityutskiy <dedekind@infradead.org>
To: Alexander Schmidt <alexs@linux.vnet.ibm.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [MTD] UBI: Per volume update marker
Date: Tue, 30 Jan 2007 21:00:20 +0200 [thread overview]
Message-ID: <1170183620.9477.157.camel@sauron> (raw)
In-Reply-To: <200701291736.01006.alexs@linux.vnet.ibm.com>
On Mon, 2007-01-29 at 17:36 +0100, Alexander Schmidt wrote:
> I removed the function from vmt unit and moved the code for checking if the
> update marker already has the given value to the vtbl unit.
I've just committed a patch which refines the semantics of the
'corrupted' flag. As I know we are going to commit your per-volume
update patch, I changed some things which otherwise maybe forgotten
correspondingly. I introduces upd_marker flag ro some data structures.
It is always 0 now, but will be used after your patch is in the
repository. I have also fixed comments assuming the per-volume update
patch is also there. Just because otherwise many of them may have been
forgotten.
I've run some tests from ubi-utils - they work. Please, send your patch
on top of my changes. I think they may even help you.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-01-30 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 9:19 [MTD] UBI: Per volume update marker Alexander Schmidt
2007-01-25 18:16 ` Artem Bityutskiy
2007-01-25 19:19 ` Josh Boyer
2007-01-26 8:47 ` Frank Haverkamp
2007-01-26 10:43 ` Artem Bityutskiy
2007-01-26 8:04 ` Artem Bityutskiy
2007-01-29 10:47 ` Alexander Schmidt
2007-01-29 13:02 ` Artem Bityutskiy
2007-01-29 16:36 ` Alexander Schmidt
2007-01-30 13:01 ` Artem Bityutskiy
2007-01-30 13:44 ` Artem Bityutskiy
2007-01-30 15:36 ` Artem Bityutskiy
2007-01-30 18:35 ` Artem Bityutskiy
2007-01-30 19:00 ` 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=1170183620.9477.157.camel@sauron \
--to=dedekind@infradead.org \
--cc=alexs@linux.vnet.ibm.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.