public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Alexander Belyakov <alexander.belyakov@intel.com>
Cc: "Korolev, Alexey" <alexey.korolev@intel.com>,
	linux-mtd@lists.infradead.org, "Kutergin,
	Timofey" <timofey.kutergin@intel.com>
Subject: Re: [PATCH/RFC] Linux MTD striping middle layer
Date: Wed, 22 Mar 2006 13:23:14 +0300	[thread overview]
Message-ID: <44212592.6080609@yandex.ru> (raw)
In-Reply-To: <44211F79.1010503@intel.com>



Alexander Belyakov wrote:
> Yes, in current implementation both blocks on subdevices, representing 
> one superblock, will be marked as bad.
BTW, using term "superblock" is not very nice IMO.

I'd offer to call it just "block" or "eraseblock", and to call 
eraseblocks of the subbevices as "sub-blocks or "sub-eraseblocks".

-- 
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.

  reply	other threads:[~2006-03-22 10:23 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 12:36 [PATCH/RFC] Linux MTD striping middle layer Belyakov, Alexander
2006-03-21 14:01 ` Vitaly Wool
2006-03-21 14:41   ` Alexander Belyakov
2006-03-21 15:11     ` Vitaly Wool
2006-03-22  9:36       ` Alexander Belyakov
2006-03-21 15:37     ` Jörn Engel
2006-03-21 16:37     ` Thomas Gleixner
2006-03-21 15:36   ` Nicolas Pitre
2006-03-21 15:09 ` Artem B. Bityutskiy
2006-03-21 18:11   ` Alexander Belyakov
2006-03-21 18:57     ` Artem B. Bityutskiy
2006-03-21 19:37       ` Nicolas Pitre
2006-03-21 20:24         ` Jörn Engel
2006-03-22  8:58         ` Artem B. Bityutskiy
2006-03-22 14:40           ` Alexander Belyakov
2006-03-22 14:47             ` Artem B. Bityutskiy
2006-03-22 15:10               ` Alexander Belyakov
2006-03-22 15:15                 ` Artem B. Bityutskiy
2006-03-22 15:39                   ` Alexander Belyakov
2006-03-22 15:45                     ` Vitaly Wool
2006-03-22 16:23                       ` Alexander Belyakov
2006-03-22 16:30                         ` Artem B. Bityutskiy
2006-03-22 19:25                         ` Vitaly Wool
2006-03-22 19:40                           ` Nicolas Pitre
2006-03-23 10:10                             ` Vitaly Wool
2006-03-22 15:51                     ` Artem B. Bityutskiy
2006-03-22  9:39       ` Alexander Belyakov
2006-03-22  9:52         ` Artem B. Bityutskiy
2006-03-22 10:26           ` Alexander Belyakov
2006-03-22 10:51             ` Artem B. Bityutskiy
2006-03-22 13:35               ` Alexander Belyakov
2006-03-22 14:40                 ` Artem B. Bityutskiy
2006-03-22 16:19                 ` Artem B. Bityutskiy
2006-03-22 16:23                   ` Artem B. Bityutskiy
2006-03-22 17:17                   ` Nicolas Pitre
2006-03-22 17:28                     ` Artem B. Bityutskiy
2006-03-22 17:50                       ` Nicolas Pitre
2006-03-21 19:08 ` Artem B. Bityutskiy
2006-03-22  9:57   ` Alexander Belyakov
2006-03-22 10:23     ` Artem B. Bityutskiy [this message]
2006-03-22 17:08 ` Artem B. Bityutskiy
2006-03-22 17:23   ` Nicolas Pitre
2006-03-23  9:39   ` Alexander Belyakov
2006-03-23 14:23     ` Nicolas Pitre
2006-03-23 14:45       ` Alexander Belyakov

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=44212592.6080609@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=alexander.belyakov@intel.com \
    --cc=alexey.korolev@intel.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=timofey.kutergin@intel.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