From: Adrian Bunk <bunk@stusta.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Simon Evans <spse@secret.org.uk>,
linux-pcmcia@lists.infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the broken MTD_PCMCIA driver
Date: Thu, 30 Nov 2006 08:09:17 +0100 [thread overview]
Message-ID: <20061130070917.GH11084@stusta.de> (raw)
In-Reply-To: <1164752187.14595.20.camel@pmac.infradead.org>
On Tue, Nov 28, 2006 at 10:16:27PM +0000, David Woodhouse wrote:
> On Sat, 2006-11-18 at 22:40 +0100, Adrian Bunk wrote:
> > The MTD_PCMCIA driver has:
> > - already been marked as BROKEN in 2.6.0 three years ago and
> > - is still marked as BROKEN.
> >
> > Drivers that had been marked as BROKEN for such a long time seem to be
> > unlikely to be revived in the forseeable future.
>
> Actually, there's hardware currently on its way to me, and I plan to fix
> this driver fairly soon.
OK.
> > But if anyone wants to ever revive this driver, the code is still
> > present in the older kernel releases.
>
> I'm unconvinced by that argument in the general case. People don't go
> looking back through git history, do they? Drivers such as this don't
> really do any harm as they are, and they're _much_ easier to find when
> someone does want to fix them up.
If there is an already merged driver that is marked as broken for a long
time, there are usually two possible cases:
- it is really unused
- patches to fix it are pending or floating around
A patch to remove a driver is usually the best way for getting the
information which case a driver belongs into (a good example might be
the zr36120 driver that seems to have found a new maintainer due to my
removal patch).
And if there's no reaction, the usefullness of very outdated and
usually non-compiling code is quite questionable.
> 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
next prev parent reply other threads:[~2006-11-30 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 21:40 [RFC: 2.6 patch] remove the broken MTD_PCMCIA driver Adrian Bunk
2006-11-28 22:16 ` David Woodhouse
2006-11-30 7:09 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-25 19:15 Adrian Bunk
2006-11-26 9:40 ` Artem Bityutskiy
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=20061130070917.GH11084@stusta.de \
--to=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=spse@secret.org.uk \
/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