All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: dedekind1@gmail.com
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Holger Brunck <holger.brunck@keymile.com>,
	Norbert van Bolhuis <nvbolhuis@aimvalley.nl>,
	Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: [PATCH v2 0/5] UBIFS: fix recovery on CFI NOR
Date: Mon, 7 Mar 2011 14:05:54 +0100	[thread overview]
Message-ID: <20110307140554.13ff94aa@wker> (raw)
In-Reply-To: <1299497990.2746.31.camel@localhost>

On Mon, 07 Mar 2011 13:39:50 +0200
Artem Bityutskiy <dedekind1@gmail.com> wrote:

> On Sun, 2011-02-06 at 15:17 +0200, Artem Bityutskiy wrote:
> > Hi,
> > 
> > here is a better patch for recovery fix. Comparing to the previous
> > patch-set now we make sure we keep write-buffer offset aligned to
> > @c->max_write_size (64 in case of CFI NOR) as much as possible.
> > 
> > Also, I've merged the "Add comments" patch with the patch which adds
> > the code.
> > 
> > You can find these patches also in the UBIFS git tree, 'cfi-nor-fix-v2'
> > branch:
> > git://git.infradead.org/ubifs-2.6.git cfi-nor-fix-v2
> > 
> > Please, test. These patches may break NAND setups as well, so anyone
> > who is interested in having stable UBIFS in the next release, please,
> > also test.
> 
> Anatolij,
> 
> did these patches fix your issues. I know you found another one related
> to unstable bits, but it is a separate issue. I need to make a decision
> whether my patches go upstream the next merge window or they should
> wait.
> 
> I have v3 of the patches, but they are not very different from v2. I
> will send them out as well.

Hi Artem,

Yes, together with both patches from
"[PATCH 0/2] Further fixes for UBIFS recovery on CFI NOR" series
these patches fix UBIFS recovery issues on our NOR flash. Remaining
issue seems to be CRC-Error due to unstable bits in UBIFS data node.

Best regards,
Anatolij

  reply	other threads:[~2011-03-07 13:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 13:17 [PATCH v2 0/5] UBIFS: fix recovery on CFI NOR Artem Bityutskiy
2011-02-06 13:17 ` [PATCH v2 1/5] UBI: incorporate maximum write size Artem Bityutskiy
2011-02-06 13:17 ` [PATCH v2 2/5] UBIFS: " Artem Bityutskiy
2011-02-06 13:17 ` [PATCH v2 3/5] UBIFS: introduce write-buffer size field Artem Bityutskiy
2011-02-06 13:17 ` [PATCH v2 4/5] UBIFS: use max_write_size for write-buffers Artem Bityutskiy
2011-02-06 13:17 ` [PATCH v2 5/5] UBIFS: use max_write_size during recovery Artem Bityutskiy
2011-02-07 16:25 ` [PATCH v2 0/5] UBIFS: fix recovery on CFI NOR Anatolij Gustschin
2011-02-07 16:43   ` Artem Bityutskiy
2011-02-07 16:58   ` Artem Bityutskiy
2011-02-07 18:06     ` Anatolij Gustschin
2011-02-08 14:33 ` Anatolij Gustschin
2011-02-08 21:31   ` Anatolij Gustschin
2011-02-10 15:01 ` [PATCH 0/2] Further fixes for UBIFS " Anatolij Gustschin
2011-02-10 15:01 ` [PATCH 1/2] UBIFS: fix no_more_nodes() to align to max_write_size Anatolij Gustschin
2011-02-10 15:06   ` Artem Bityutskiy
2011-02-10 15:01 ` [PATCH 2/2] mtd: cfi: fix writebufsize initialization Anatolij Gustschin
2011-02-10 15:13   ` Guillaume LECERF
2011-02-10 15:27     ` Artem Bityutskiy
2011-02-11 12:04     ` Anatolij Gustschin
2011-02-11 12:25       ` Guillaume LECERF
2011-02-11 14:36   ` Artem Bityutskiy
2011-02-11 15:05     ` Guillaume LECERF
2011-02-11 15:32   ` Artem Bityutskiy
2011-02-11 13:45 ` [PATCH v2 0/5] UBIFS: fix recovery on CFI NOR Artem Bityutskiy
2011-03-07 11:39 ` Artem Bityutskiy
2011-03-07 13:05   ` Anatolij Gustschin [this message]
2011-03-07 13:51     ` Artem Bityutskiy
2011-03-07 17:06       ` Anatolij Gustschin

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=20110307140554.13ff94aa@wker \
    --to=agust@denx.de \
    --cc=adrian.hunter@nokia.com \
    --cc=dedekind1@gmail.com \
    --cc=holger.brunck@keymile.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nvbolhuis@aimvalley.nl \
    /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.