linux-kernel - Re: [RFC: 2.6 patch] remove the broken MTD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1164752187.14595.20.camel@pmac.infradead.org>
Date:	Tue, 28 Nov 2006 22:16:27 +0000
From:	David Woodhouse <dwmw2@...radead.org>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Simon Evans <spse@...ret.org.uk>, linux-pcmcia@...ts.infradead.org,
	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the broken MTD_PCMCIA driver

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.

> 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.

-- 
dwmw2

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/