public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: xiaochuan-xu <xiaochuan-xu@cqu.edu.cn>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 4/4] UBI WL-Subsys: Improvement in prot tree
Date: Tue, 09 Dec 2008 15:03:23 +0200	[thread overview]
Message-ID: <1228827803.13686.189.camel@sauron> (raw)
In-Reply-To: <1228823163.2753.18.camel@localhost.localdomain>

On Tue, 2008-12-09 at 19:46 +0800, xiaochuan-xu wrote:
> >From e3af46580d374fc5da79212c17ef9f0179299bd0 Mon Sep 17 00:00:00 2001
> From: Xiaochuan-Xu <xiaochuan-xu@cqu.edu.cn>
> Date: Tue, 9 Dec 2008 19:27:40 +0800
> Subject: [PATCH] Adjust severial macros
> 
> In order to fulfill the identical function of the currenty
> prot RB-tree. *_PROTECTION macros are increased respectively
> 
> Signed-off-by: Xiaochuan-Xu <xiaochuan-xu@cqu.edu.cn>
> ---
>  drivers/mtd/ubi/wl.c |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/mtd/ubi/wl.c b/drivers/mtd/ubi/wl.c
> index 0b1e8c7..603435f 100644
> --- a/drivers/mtd/ubi/wl.c
> +++ b/drivers/mtd/ubi/wl.c
> @@ -130,9 +130,9 @@
>   * How many erase cycles are short term, unknown, and long term physical
>   * eraseblocks protected.
>   */
> -#define ST_PROTECTION 16
> -#define U_PROTECTION  10
> -#define LT_PROTECTION 4
> +#define ST_PROTECTION 17
> +#define U_PROTECTION  11
> +#define LT_PROTECTION 5

I doubt these constants make much sense. I would suggest you to get rid
of them and simplify things. Let's have only one constant instead of 3.
This will allow us to implement efficient protection queue which you
will not need to walk at all.

So I'd suggest you to send a separate "preparation" patch which
introduces one constant instead of 3. E.g.,

#define PROTECTION 10

It may be re-named to PROT_LIST_LEN later, probably.

How does this plan sound to you?

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

  parent reply	other threads:[~2008-12-09 13:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1228823163.2753.18.camel@localhost.localdomain>
2008-12-09 11:46 ` [PATCH 4/4] UBI WL-Subsys: Improvement in prot tree xiaochuan-xu
2008-12-09 13:03 ` Artem Bityutskiy [this message]
     [not found]   ` <1228884752.3225.80.camel@localhost.localdomain>
2008-12-10  4:52     ` xiaochuan-xu
2008-12-10  8:44     ` Artem Bityutskiy
     [not found]       ` <1228914665.3655.31.camel@localhost.localdomain>
2008-12-10 13:11         ` xiaochuan-xu
2008-12-10 13:35         ` Artem Bityutskiy
     [not found]       ` <1228913251.3655.10.camel@localhost.localdomain>
     [not found]         ` <1228931859.13686.350.camel@sauron>
     [not found]           ` <1228981865.2702.9.camel@localhost.localdomain>
     [not found]             ` <1229022841.13686.384.camel@sauron>
     [not found]               ` <1229332169.5306.1.camel@localhost.localdomain>
     [not found]                 ` <1229332781.13686.447.camel@sauron>
     [not found]                   ` <1229343610.2687.52.camel@localhost.localdomain>
     [not found]                     ` <1229343746.4911.2.camel@sauron>
     [not found]                       ` <1229347894.2687.56.camel@localhost.localdomain>
     [not found]                         ` <1229356809.4911.57.camel@sauron>
     [not found]                           ` <1229394788.2691.14.camel@localhost.localdomain>
2008-12-16  2:33                             ` xiaochuan-xu
     [not found]                           ` <1229395691.2691.18.camel@localhost.localdomain>
2008-12-16  2:48                             ` xiaochuan-xu
2008-12-16  6:36                             ` 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=1228827803.13686.189.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=xiaochuan-xu@cqu.edu.cn \
    /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