From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Richard Weinberger <richard@nod.at>
Cc: Heinz.Egger@linutronix.de, tglx@linutronix.de,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
tim.bird@am.sony.com
Subject: Re: [PATCH 01/10] UBI: Add fastmap on-flash data structures
Date: Wed, 26 Sep 2012 13:33:11 +0300 [thread overview]
Message-ID: <1348655591.24309.64.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1348511492-91606-2-git-send-email-richard@nod.at>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Mon, 2012-09-24 at 20:31 +0200, Richard Weinberger wrote:
> Add the on-flash data structures neeed by fastmap
> to ubi-media.h
>
> Signed-off-by: Richard Weinberger <richard@nod.at>
Richard, thanks, here is the deal I suggest
1. I do not really have time to review this in details.
2. I do not want to block this either
3. I want to merge this to 3.7 with come pre-conditions (see below)
as "Experimental" with a claim that the on-flash format can
be changed. Something like Linus did for btrfs. Then let people
play with fastmap. I am sure it'll need changes when people
try to use it in production.
a. Aiaiai is happy
b. You provide a section for the mtd web site describing fastmap
c. It does not break anything when it is disabled
d. When it is enabled, it also passes the UBI tests
Actually, I want to expose it to linux-next already after step a.
Despite a lot of testing you have already done, I am willing to do some
testing myself as well, so I'll do c. and d. and let you know if there
are issues.
Could you please do b. ?
--
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-09-26 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 18:31 UBI: Fastmap request for inclusion (v18) Richard Weinberger
2012-09-24 18:31 ` [PATCH 01/10] UBI: Add fastmap on-flash data structures Richard Weinberger
2012-09-26 10:33 ` Artem Bityutskiy [this message]
2012-09-26 15:54 ` Richard Weinberger
2012-09-24 18:31 ` [PATCH 02/10] UBI: Add fastmap stuff to ubi.h Richard Weinberger
2012-09-24 18:31 ` [PATCH 03/10] UBI: Export next_sqnum() Richard Weinberger
2012-09-24 18:31 ` [PATCH 04/10] UBI: Add self_check_eba() Richard Weinberger
2012-09-24 18:31 ` [PATCH 05/10] UBI: Add fastmap bits to build.c Richard Weinberger
2012-09-24 18:31 ` [PATCH 06/10] UBI: Wire-up ->fm_sem Richard Weinberger
2012-09-24 18:31 ` [PATCH 07/10] UBI: Add fastmap stuff to attach.c Richard Weinberger
2012-09-24 18:31 ` [PATCH 08/10] UBI: Add fastmap support to the WL sub-system Richard Weinberger
2012-09-24 18:31 ` [PATCH 09/10] UBI: Add fastmap core Richard Weinberger
2012-09-24 18:31 ` [PATCH 10/10] UBI: Wire-up fastmap Richard Weinberger
2012-09-26 12:22 ` UBI: Fastmap request for inclusion (v18) Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2012-09-26 15:51 UBI: Fastmap request for inclusion (v19) Richard Weinberger
2012-09-26 15:51 ` [PATCH 01/10] UBI: Add fastmap on-flash data structures Richard Weinberger
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=1348655591.24309.64.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=Heinz.Egger@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox