From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [84.204.75.166] (helo=shelob.oktetlabs.ru) by canuck.infradead.org with esmtps (Exim 4.54 #1 (Red Hat Linux)) id 1FPEeH-0007v4-Cj for linux-mtd@lists.infradead.org; Fri, 31 Mar 2006 03:07:05 -0500 Message-ID: <442CE2DC.7020505@yandex.ru> Date: Fri, 31 Mar 2006 12:05:48 +0400 From: "Artem B. Bityutskiy" MIME-Version: 1.0 To: "Artem B. Bityutskiy" References: <442B9FA5.9070901@ru.mvista.com> <442BF839.8060402@intel.com> <1143733184.3579.47.camel@sauron.oktetlabs.ru> <442CD50A.6070006@intel.com> <442CE217.8080103@yandex.ru> In-Reply-To: <442CE217.8080103@yandex.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Belyakov , Vitaly Wool , "Kutergin, Timofey" , "Korolev, Alexey" , linux-mtd@lists.infradead.org Subject: Re: [PATCH/RFC] MTD: Striping layer core List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Artem B. Bityutskiy wrote: > Good question. I think you could report this is a striped device > (introducing an MTD_STRIPED option). Also you may provide a > stripe_get_info(struct mtd_info *mtd) function which will return a > struct stripe_info object describing this striped device, including the > components it consists of. Err, and I believe you *have to* report mtd type as MTD_STRIPED. -- Best Regards, Artem B. Bityutskiy, St.-Petersburg, Russia.