All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com
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: [RFC v5] UBI: Fastmap support (aka checkpointing)
Date: Thu, 17 May 2012 13:50:43 +0200	[thread overview]
Message-ID: <4FB4E613.4020100@nod.at> (raw)
In-Reply-To: <1337225964.2730.11.camel@brekeke>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

Am 17.05.2012 05:39, schrieb Artem Bityutskiy:
> On Wed, 2012-05-16 at 22:51 +0200, Richard Weinberger wrote:
>> This is a bug-fix release. v4 handled static volumes wrong.
>> v6 will address everything that Artem pointed out.
> 
> Hi, I'll try to review this further, but few points I'd like to
> highlight.
> 
> 1. We'll need to re-structure the code a bit and rename scan.[ch] to
> attach.[ch], all data structures like 'struct ubi_scan_volume' which you
> re-use we will also need to rename and remove the "scan" word, etc. I am
> willing to do this preparation.

No problem. It's already on my list.

> 2. You need to re-use the scanning code we have for scanning the fastmap
> volumes, I think. May be you need some amendments there, but currently
> you have more duplication than needed. You'll just plug more of your
> code to the attach.c file: check if there fastmap, if yes, read it and
> scan the internal fastmap volumes by re-using functions in attach.c. So
> all the fastmap reading/checking/manipulating stuff is in fastmap.c, the
> scanning and interpreting is in attach.c.

Okay.

> Again, I am willing to do corresponding preparations for you, you'll
> need to amend your code then.

As I said, v6 will contain all requested changes.

> Also, I think you probably do not have to split your patches. For me it
> looks like there is a lot of work needed anyway, so you could just send
> it as one patch so far, to make things easier. Because reviewing this
> stuff by reading patches is too difficult anyway, and the reviewer has
> to apply it and review / navigate the real code, and just look sometimes
> to the patch.
> 

Will do.

Thanks,
//richard


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, Heinz.Egger@linutronix.de,
	tim.bird@am.sony.com
Subject: Re: [RFC v5] UBI: Fastmap support (aka checkpointing)
Date: Thu, 17 May 2012 13:50:43 +0200	[thread overview]
Message-ID: <4FB4E613.4020100@nod.at> (raw)
In-Reply-To: <1337225964.2730.11.camel@brekeke>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

Am 17.05.2012 05:39, schrieb Artem Bityutskiy:
> On Wed, 2012-05-16 at 22:51 +0200, Richard Weinberger wrote:
>> This is a bug-fix release. v4 handled static volumes wrong.
>> v6 will address everything that Artem pointed out.
> 
> Hi, I'll try to review this further, but few points I'd like to
> highlight.
> 
> 1. We'll need to re-structure the code a bit and rename scan.[ch] to
> attach.[ch], all data structures like 'struct ubi_scan_volume' which you
> re-use we will also need to rename and remove the "scan" word, etc. I am
> willing to do this preparation.

No problem. It's already on my list.

> 2. You need to re-use the scanning code we have for scanning the fastmap
> volumes, I think. May be you need some amendments there, but currently
> you have more duplication than needed. You'll just plug more of your
> code to the attach.c file: check if there fastmap, if yes, read it and
> scan the internal fastmap volumes by re-using functions in attach.c. So
> all the fastmap reading/checking/manipulating stuff is in fastmap.c, the
> scanning and interpreting is in attach.c.

Okay.

> Again, I am willing to do corresponding preparations for you, you'll
> need to amend your code then.

As I said, v6 will contain all requested changes.

> Also, I think you probably do not have to split your patches. For me it
> looks like there is a lot of work needed anyway, so you could just send
> it as one patch so far, to make things easier. Because reviewing this
> stuff by reading patches is too difficult anyway, and the reviewer has
> to apply it and review / navigate the real code, and just look sometimes
> to the patch.
> 

Will do.

Thanks,
//richard


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-05-17 11:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 20:51 [RFC v5] UBI: Fastmap support (aka checkpointing) Richard Weinberger
2012-05-16 20:51 ` Richard Weinberger
2012-05-16 20:51 ` [PATCH 1/7] [RFC] UBI: Export next_sqnum() Richard Weinberger
2012-05-16 20:51   ` Richard Weinberger
2012-05-17 12:12   ` Artem Bityutskiy
2012-05-17 12:12     ` Artem Bityutskiy
2012-05-16 20:51 ` [PATCH 2/7] [RFC] UBI: Export compare_lebs() Richard Weinberger
2012-05-16 20:51   ` Richard Weinberger
2012-05-16 20:51 ` [PATCH 3/7] [RFC] UBI: Add fastmap on-flash layout Richard Weinberger
2012-05-16 20:51   ` Richard Weinberger
2012-05-16 20:51 ` [PATCH 4/7] [RFC] UBI: Add fastmap structs to ubi_device Richard Weinberger
2012-05-16 20:51   ` Richard Weinberger
2012-05-16 20:52 ` [PATCH 5/7] [RFC] UBI: Make wl subsystem fastmap aware Richard Weinberger
2012-05-16 20:52   ` Richard Weinberger
2012-05-16 20:52 ` [PATCH 6/7] [RFC] UBI: Implement fastmapping support Richard Weinberger
2012-05-16 20:52   ` Richard Weinberger
2012-05-16 20:52 ` [PATCH 7/7] [RFC] UBI: Wire up fastmap support Richard Weinberger
2012-05-16 20:52   ` Richard Weinberger
2012-05-17  3:39 ` [RFC v5] UBI: Fastmap support (aka checkpointing) Artem Bityutskiy
2012-05-17  3:39   ` Artem Bityutskiy
2012-05-17 11:50   ` Richard Weinberger [this message]
2012-05-17 11:50     ` Richard Weinberger
2012-05-17 11:57     ` Artem Bityutskiy
2012-05-17 11:57       ` Artem Bityutskiy
2012-05-17 12:02     ` Artem Bityutskiy
2012-05-17 12:02       ` Artem Bityutskiy
2012-05-17 12:04       ` Richard Weinberger
2012-05-17 12:04         ` 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=4FB4E613.4020100@nod.at \
    --to=richard@nod.at \
    --cc=Heinz.Egger@linutronix.de \
    --cc=dedekind1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --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 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.