From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751365AbWBVQfU (ORCPT ); Wed, 22 Feb 2006 11:35:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751362AbWBVQfU (ORCPT ); Wed, 22 Feb 2006 11:35:20 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:65506 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1751365AbWBVQfS (ORCPT ); Wed, 22 Feb 2006 11:35:18 -0500 Date: Wed, 22 Feb 2006 16:35:11 +0000 From: Christoph Hellwig To: David Zeuthen Cc: Linus Torvalds , Kay Sievers , Pekka J Enberg , Greg KH , Adrian Bunk , Robert Love , Andrew Morton , Linux Kernel Mailing List , John Stultz Subject: Re: 2.6.16-rc4: known regressions Message-ID: <20060222163511.GA18694@infradead.org> Mail-Followup-To: Christoph Hellwig , David Zeuthen , Linus Torvalds , Kay Sievers , Pekka J Enberg , Greg KH , Adrian Bunk , Robert Love , Andrew Morton , Linux Kernel Mailing List , John Stultz References: <84144f020602190306o3149d51by82b8ccc6108af012@mail.gmail.com> <20060219145442.GA4971@stusta.de> <1140383653.11403.8.camel@localhost> <20060220010205.GB22738@suse.de> <1140562261.11278.6.camel@localhost> <20060221225718.GA12480@vrfy.org> <20060222152743.GA22281@vrfy.org> <1140625103.21517.18.camel@daxter.boston.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1140625103.21517.18.camel@daxter.boston.redhat.com> User-Agent: Mutt/1.4.2.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 22, 2006 at 11:18:22AM -0500, David Zeuthen wrote: > For just one example of API breaking see > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175998 > > This breaks stuff for end users in a stable distribution. Not good. That's not an API breakage. The API is left untouched, the driver now just reports the attached device as what it is. If HAL wasn't a piece of cargo-cult programming crap you'd see in the relevant standards what scsi device types exist, or even better stop relying on such low-level knowledge. It's a disk if sd_mod attaches to it is a much better rule than relying on lowlevel SAM details.