linux-kernel - Re: [PATCH] remove old broken Cobalt LCD driver

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: <20080716171818.0e6a45b1.akpm@linux-foundation.org>
Date:	Wed, 16 Jul 2008 17:18:18 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	yoichi_yuasa@...peaks.co.jp, ralf@...ux-mips.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] remove old broken Cobalt LCD driver

On Wed, 16 Jul 2008 17:16:40 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Tue, 15 Jul 2008 22:31:32 +0900
> Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp> wrote:
> 
> > Remove old broken Cobalt LCD driver.
> > 
> > Signed-off-by: Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>
> 
> Why do we remove it, rather than unbreaking it?
> 
> Did some other driver replace it?  Does nobody need the driver any
> more?

doh.  That's what I get for processing patches in reverse-time-order.

So there's no point in retaining both the old driver and the new one
for some period of time?

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