public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Vitaly Wool <vwool@ru.mvista.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org, kbaidarov <kbaidarov@dev.rtsoft.ru>
Subject: Re: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD
Date: Mon, 20 Nov 2006 15:15:28 +0300	[thread overview]
Message-ID: <45619C60.7070400@ru.mvista.com> (raw)
In-Reply-To: <1163856955.5597.71.camel@sauron>

Artem Bityutskiy wrote:
> On Sat, 2006-11-18 at 07:33 -0600, Josh Boyer wrote:
>   
>> Because we've consistently told people not to do that.
>>     
>
> OK, but why ?
>
>   
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 ;-)

Vitaly

  parent reply	other threads:[~2006-11-20 12: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 [this message]
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
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=45619C60.7070400@ru.mvista.com \
    --to=vwool@ru.mvista.com \
    --cc=dedekind@infradead.org \
    --cc=kbaidarov@dev.rtsoft.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox