From: Konstantin Baydarov <kbaidarov@dev.rtsoft.ru>
To: dedekind@infradead.org
Cc: Vitaly Wool <vwool@ru.mvista.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD
Date: Mon, 20 Nov 2006 16:20:03 +0300 [thread overview]
Message-ID: <4561AB83.3070001@dev.rtsoft.ru> (raw)
In-Reply-To: <1164026819.5597.88.camel@sauron>
Artem Bityutskiy wrote:
> On Mon, 2006-11-20 at 15:15 +0300, Vitaly Wool wrote:
>
>>B/c it introduces new fields in generic mtd structures which are already
>>overcomplicated, and modifies a lot of generic code. I'd expect that
>>with this patch applied stuff like mtdcore.c and mtdpart.c becomes
>>exposed to possible licensing issues which is definitely not what we aim ;-)
>
>
> I am talking about something like this:
>
> http://lists.infradead.org/pipermail/linux-mtd/2004-May/009683.html
>
> I do not see it introducing any new field.
>
I realized it exactly the same way on top of readoly block device.
Patch, you talking about, definitely needs #ifdef-s and it waste kernel
RAM statically allocating block_map, block_top, block_scantop
MAX_MTD_DEVICES times :-).
next prev parent reply other threads:[~2006-11-20 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 15:40 [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD kbaidarov
2006-11-18 13:15 ` Artem Bityutskiy
2006-11-18 13:33 ` Josh Boyer
2006-11-18 13:35 ` Artem Bityutskiy
2006-11-18 13:40 ` Artem Bityutskiy
2006-11-20 12:15 ` Vitaly Wool
2006-11-20 12:46 ` Artem Bityutskiy
2006-11-20 13:06 ` Vitaly Wool
2006-11-20 13:39 ` Artem Bityutskiy
2006-11-20 13:20 ` Konstantin Baydarov [this message]
2006-11-20 12:11 ` Vitaly Wool
2006-11-20 12:05 ` Vitaly Wool
2006-11-20 14:52 ` Josh Boyer
2006-11-21 10:30 ` Vitaly Wool
2006-11-22 16:56 ` Konstantin Baydarov
2006-12-02 16:41 ` Konstantin Baydarov
2007-09-27 15:05 ` Gregory CLEMENT
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=4561AB83.3070001@dev.rtsoft.ru \
--to=kbaidarov@dev.rtsoft.ru \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vwool@ru.mvista.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