All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: brijesh.singh@calsoftinc.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI Patch: Max Sequence no not updated in scan.c
Date: Fri, 06 Jul 2007 12:46:54 +0300	[thread overview]
Message-ID: <1183715214.3531.53.camel@sauron> (raw)
In-Reply-To: <31331.172.16.0.34.1183712408.squirrel@webmail.calsoftinc.com>

On Fri, 2007-07-06 at 14:30 +0530, brijesh.singh@calsoftinc.com wrote:
> Hi,I came across problem of having two leb with same sequence no.This
> happens when we continuously write one block again and again and reboot
> machine before background thread erases those blocks.
> The problem here was,when we find two blocks with same sequence no,we take
> the higher one,but we were not updating max seq no,so next block may have
> the same seqnum.
> This patch solves this problem.

I've committed your patch (modified) and one more fix, please, try.

Thanks,
Artem.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

      parent reply	other threads:[~2007-07-06  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  9:00 UBI Patch: Max Sequence no not updated in scan.c brijesh.singh
2007-07-06  9:22 ` Artem Bityutskiy
2007-07-06  9:46 ` 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=1183715214.3531.53.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=brijesh.singh@calsoftinc.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.