public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers
Date: Sun, 8 Jan 2006 01:24:57 +0100	[thread overview]
Message-ID: <20060108002457.GE3774@stusta.de> (raw)
In-Reply-To: <1136678409.30348.26.camel@pmac.infradead.org>

On Sun, Jan 08, 2006 at 12:00:09AM +0000, David Woodhouse wrote:
> On Sat, 2006-01-07 at 23:07 +0100, Adrian Bunk wrote:
> > This patch brings the MTD_SHARP driver back into life and removes the 
> > non-compiling MTD_AMDSTD and MTD_JEDEC with everything depending on 
> > them.
> 
> Please provide further background on your reasoning. I'll enumerate my
> questions to make it easy for you to answer each one fully.
> 
> 1. Precisely when were these chip drivers marked obsolete?

Since kernel 2.4.11-pre4, released Thu, 4 Oct 2001 20:47:23 -0700.

> 2. What was the reason for marking them obsolete?

The changelog says:
 - David Woodhouse: large MTD and JFFS[2] update

> 3. What are the factors which led you to conclude that _now_ is the time
> to actually remove them?

http://lkml.org/lkml/2005/12/12/43

> 4. What are the factors which led you to _remove_ the map drivers which
> currently use the obsolete chip drivers, rather than taking the obvious
> alternative solution for those map drivers?

It seems that for one and a half years noone considered it a problem 
that they were no longer available...

> dwmw2

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

  reply	other threads:[~2006-01-08  0:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 22:07 [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers Adrian Bunk
2006-01-08  0:00 ` David Woodhouse
2006-01-08  0:24   ` Adrian Bunk [this message]
2006-01-08  0:38     ` David Woodhouse
2006-01-08  1:45       ` Andrew Morton
2006-01-08 12:41         ` David Woodhouse
2006-01-08 12:57           ` Adrian Bunk
2006-01-08 13:06             ` David Woodhouse
2006-01-08 14:14               ` [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN Adrian Bunk
2006-01-08 14:24                 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2006-01-06 18:14 [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers Adrian Bunk

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=20060108002457.GE3774@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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