public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: MTD list <linux-mtd@lists.infradead.org>
Subject: [PATCH v3 0/7] UBIFS: fix recovery on CFI NOR
Date: Tue,  8 Mar 2011 10:32:41 +0200	[thread overview]
Message-ID: <1299573168-27760-1-git-send-email-dedekind1@gmail.com> (raw)

Hi,

here is the third version of the patches. The differences to v2 are
as follows.

1. UBI now exports the LEB start offset. UBIFS uses this to figure out
   whether the LEB starts at the max_write_size-aligned boundary or
   not.
2. The bugfix in recovery.c is included.

I've also pushed these patches to the master and linux-next branches of
the ubifs-2.6.git tree, and the plan is to merge them upstream.

Note, the "mtd: cfi: fix writebufsize initialization" patch from Anatolij,
which fixes mtd->writebufsize when there is interleaving and which is also
necessary to fix UBIFS recovery on CFI NOR, should be merged upstream via
the MTD tree, and it is currently sitting in my l2-mtd-2.6.git tree.

Artem.

             reply	other threads:[~2011-03-08  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  8:32 Artem Bityutskiy [this message]
2011-03-08  8:32 ` [PATCH v3 1/7] UBI: incorporate maximum write size Artem Bityutskiy
2011-03-08  8:32 ` [PATCH v3 2/7] UBI: provide LEB offset information Artem Bityutskiy
2011-03-08  8:32 ` [PATCH v3 3/7] UBIFS: incorporate maximum write size Artem Bityutskiy
2011-03-08  8:32 ` [PATCH v3 4/7] UBI: incorporate LEB offset information Artem Bityutskiy
2011-03-08  8:32 ` [PATCH v3 5/7] UBIFS: introduce write-buffer size field Artem Bityutskiy
2011-03-08  8:32 ` [PATCH v3 6/7] UBIFS: use max_write_size for write-buffers Artem Bityutskiy
2011-03-08  8:32 ` [PATCH v3 7/7] UBIFS: use max_write_size during recovery 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=1299573168-27760-1-git-send-email-dedekind1@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=agust@denx.de \
    --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