Re: hung bootup with "drm/radeon/kms: move radeon KMS on/off switch out of staging."

[Ingo Molnar <mingo@elte.hu>]

* Matthew Garrett <mjg59@srcf.ucam.org> 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