All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Aleksander Sanochkin <asanochkin@Lnxw.COM>
Cc: linux-mtd@lists.infradead.org, jffs-dev@axis.com
Subject: Re: JFFS1/MTD bug-fixes
Date: Mon, 03 Dec 2001 15:55:01 +0000	[thread overview]
Message-ID: <11102.1007394901@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112030726090.14716-100000@newbast.lynuxworks.com>

asanochkin@Lnxw.COM said:
> 
>  1) To be consistent with cfi_cmdset_002.c which always initializes
>     eraseregions.
>  2) We have also modified JFFS1 code so as it now works for flash
>     partitions with non-uniform sectors, and our code is based on
>     the assumption that eraseregions are always initialized. 

If possible, I would prefer to keep the individual listing of erase regions
optional for the common case where it's not necessary - how difficult would
it be to make the JFFS1 code deal with that?

>  We have also added a possibility for run-time partitioning of an MTD
> device, and use this usage_counter to prevent deleting of a partition
> while it is being used by some process.

In that context, I agree that it makes sense. Have you seen Jörn Engel's
rewrite of the partitioning code, which I was intending to look at merging
in 2.5? It would be useful to make that does what you require before we
merge it.

--
dwmw2

  reply	other threads:[~2001-12-03 15:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 15:36 JFFS1/MTD bug-fixes Aleksander Sanochkin
2001-12-03 15:55 ` David Woodhouse [this message]
2001-12-04  9:07   ` Jörn Engel
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 13:11 Aleksander Sanochkin
2001-12-07 15:34 ` Jörn Engel
2001-12-07 13:07 Aleksander Sanochkin
2001-12-07 15:40 ` Jörn Engel
2001-12-04 16:36 Aleksander Sanochkin
2001-12-04 22:18 ` Jörn Engel
2001-12-04 16:30 Aleksander Sanochkin
2001-12-04 22:44 ` Jörn Engel
2001-11-30 17:29 Aleksander Sanochkin
2001-12-01 10:47 ` David Woodhouse

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=11102.1007394901@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=asanochkin@Lnxw.COM \
    --cc=jffs-dev@axis.com \
    --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 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.