From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Nikita V. Youshchenko" <nyoushchenko@mvista.com>
Cc: Richard Weinberger <richard@nod.at>,
Rob Taylor <rtaylor@mvista.com>,
Alexander Kaliadin <akaliadin@mvista.com>,
linux-mtd@lists.infradead.org, Pavan Jadhav <pjadhav@mvista.com>
Subject: Re: ubi_update_fastmap: could not find an early PEB
Date: Wed, 27 Jun 2012 13:56:26 +0300 [thread overview]
Message-ID: <1340794586.29342.52.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <201206222126.12515@blacky.localdomain>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
On Fri, 2012-06-22 at 21:26 +0400, Nikita V. Youshchenko wrote:
> > > How to overcome this?
> >
> > Can you please try the attached patch?
> > This patch allows the WL-worker to produce free anchor PEBS.
>
> This patch does not apply against 'fastmap' branch of
> git://git.infradead.org/linux-ubi.git
>
> And incompatibility is big enough to be not obviously resolvable.
I've just pushed out the latest work of Richard to the "fastmap" branch,
should be up-to-date now. Thanks for feed-back, testing is very
appreciated and certainly should help merging this faster.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-27 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 16:05 ubi_update_fastmap: could not find an early PEB Nikita V. Youshchenko
2012-06-22 16:32 ` Richard Weinberger
2012-06-22 17:26 ` Nikita V. Youshchenko
2012-06-22 17:37 ` Richard Weinberger
2012-06-22 18:46 ` Nikita V. Youshchenko
2012-06-22 18:49 ` Richard Weinberger
2012-06-27 10:56 ` Artem Bityutskiy [this message]
2012-06-27 11:00 ` Richard Weinberger
2012-06-27 11:07 ` Nikita V. Youshchenko
2012-06-27 12:15 ` 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=1340794586.29342.52.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=akaliadin@mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nyoushchenko@mvista.com \
--cc=pjadhav@mvista.com \
--cc=richard@nod.at \
--cc=rtaylor@mvista.com \
/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.