Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755783AbXFUGdQ (ORCPT ); Thu, 21 Jun 2007 02:33:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751443AbXFUGdB (ORCPT ); Thu, 21 Jun 2007 02:33:01 -0400 Received: from brick.kernel.dk ([80.160.20.94]:22727 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751242AbXFUGdA (ORCPT ); Thu, 21 Jun 2007 02:33:00 -0400 Date: Thu, 21 Jun 2007 08:32:12 +0200 From: Jens Axboe To: Rene Herman Cc: Christoph Hellwig , Boaz Harrosh , linux-scsi , linux-kernel@vger.kernel.org Subject: Re: [PATCH] fix req->cmd == INT cases Message-ID: <20070621063210.GY18863@kernel.dk> References: <4677FD50.2090803@panasas.com> <20070619171610.GH18863@kernel.dk> <4679072C.2010604@panasas.com> <20070620122247.GA4443@infradead.org> <20070620122409.GU18863@kernel.dk> <46799948.8000106@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46799948.8000106@gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2150 Lines: 56 On Wed, Jun 20 2007, Rene Herman wrote: > On 06/20/2007 02:24 PM, Jens Axboe wrote: > > >On Wed, Jun 20 2007, Christoph Hellwig wrote: > >>On Wed, Jun 20, 2007 at 01:53:32PM +0300, Boaz Harrosh wrote: > > >>> drivers/cdrom/aztcd.c > >>> drivers/cdrom/cm206.c > >>> drivers/cdrom/gscd.c > >>> drivers/cdrom/mcdx.c > >>> drivers/cdrom/optcd.c > >>> drivers/cdrom/sjcd.c > >>> > >>These are old cdrom drivers that are broken in various ways and > >>probably should be killed off aswell. > > > >I agree (with both sentiments), would anyone mind if I just killed them > >off? > > I wouldn't. As far as I'm concerned everything in drivers/cdrom except > viocd.c and cdrom.c itself can go, assuming I'll be allowed to bring back > support for the legacy cdrom types I'd still like to have supported -- in > the first place mitsumi (mcdx), panasonic (sbpcd) and sony (cdu31a) and > perhaps at some point other types if/when I happen across the hardware. Sure, a working clean driver would always be allowed in. I'll remove the legacy drivers in 2.6.23. > The old drivers serve as a source of hardware information but at least > mcdx was broken in so many ways that it only did so at the source > level. When I wanted to check throughput with the old driver I > actually had to go back as far as 2.0.34 to find a working driver (the > old mcd.c, already removed since 2.6.10). 2.0.34 sources are available > from kernel.org, and 2.6.22 sources even from my local machine... Heh, that's pretty scary! > >mitsumi support is being reworked, that can get reintroduced once the > >driver is in a stable state. > > ... which, by the way, is still waiting on comment from anyone with a clue > as to why it makes the machine go boom (easily repeatable when using CFQ, > not or not easily when using AS): > > http://lkml.org/lkml/2007/6/4/50 Yeah I know, I will get around to it eventually. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/