Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932388Ab0BDTTy (ORCPT ); Thu, 4 Feb 2010 14:19:54 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:58995 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932078Ab0BDTTx (ORCPT ); Thu, 4 Feb 2010 14:19:53 -0500 Date: Thu, 4 Feb 2010 20:19:35 +0100 From: Ingo Molnar To: Matthew Garrett Cc: Dave Airlie , Dave Airlie , torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, dri-devel@lists.sf.net Subject: Re: hung bootup with "drm/radeon/kms: move radeon KMS on/off switch out of staging." Message-ID: <20100204191935.GC6665@elte.hu> References: <20100204071705.GA28403@elte.hu> <20100204164859.GA17878@srcf.ucam.org> <20100204170826.GA16397@elte.hu> <20100204173602.GA19855@srcf.ucam.org> <20100204175445.GB27361@elte.hu> <20100204175928.GA20595@srcf.ucam.org> <20100204181218.GA6175@elte.hu> <20100204181540.GA20922@srcf.ucam.org> <20100204185603.GA6665@elte.hu> <20100204190012.GA21950@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100204190012.GA21950@srcf.ucam.org> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 37 * Matthew Garrett wrote: > On Thu, Feb 04, 2010 at 07:56:03PM +0100, Ingo Molnar wrote: > > > Do you see my argument why any user who is hit by this would categorize > > this as a kernel regression in an existing driver? > > No. If a user changes configuration and gets a hang, that's a bug but not a > regression. Only if it's some brand-new driver or a brand-new kernel feature for which no-one can have any prior expectations of stability. Especially if it's added in the merge window when many new drivers are added. But isnt it a regression to a user if it's shipped in -rc7 appearing as a new sub-option of an existing driver? I'd wager that most main-street Linux users would consider that a regression. As i see it is that you are trying to have it both ways: claim it's a new driver when it comes to handling regressions, but also try to have the benefits (and adoption flux) of an old driver when it comes to facing it to users. Some info about that in the Kconfig would be helpful IMO - so that people are less surprised if it happens to break while the radeon driver worked fine for them before. Thanks, Ingo -- 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/