From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757941AbaEKJwA (ORCPT <rfc822;w@1wt.eu>);
	Sun, 11 May 2014 05:52:00 -0400
Received: from cantor2.suse.de ([195.135.220.15]:38965 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754825AbaEKJv5 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sun, 11 May 2014 05:51:57 -0400
Date: Sun, 11 May 2014 11:51:51 +0200
Message-ID: <s5h4n0wod6w.wl%tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Fubo Chen <fubo.chen@gmail.com>
Cc: =?UTF-8?B?TmljY29sw7I=?= Belli <darkbasic@linuxsystems.it>,
        Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf
In-Reply-To: <CAJAFBLBjW3v_qmOiU+0V2AuwgOV2bXRGdZtpUAoDDJuq0ZtEKQ@mail.gmail.com>
References: <CAJAFBLBjW3v_qmOiU+0V2AuwgOV2bXRGdZtpUAoDDJuq0ZtEKQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

At Sun, 11 May 2014 10:49:37 +0200,
Fubo Chen wrote:
> 
> (adding Takashi Iwai)
> 
> On Thu, May 8, 2014 at 4:06 PM, Niccolò Belli <darkbasic@linuxsystems.it> wrote:
> > Hi,
> > Sorry for posting on linux-kernel but from my experience nobody ever looks
> > at the kernel bug tracker and I would like to get it fixed before 3.15 gets
> > released.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=75671
> >
> > It's funny to read "Still no boot quirks are called, *so it might not work
> > well on some devices*" in the commit description:
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=400362f1d8dcfda3562e80e88cfc2a92cffaf9bf
> > Why does code known to be broken hit the Linus tree? Every new kernel
> > release there is something broken to bisect, it doesn't matter if you wait
> > for the stable release or not. That's frustrating for an end user.

The bug was already fixed recently in the latest Linus tree or sound
git tree.

The sentence was misread: "it might not work" just means that it's not
tested by these specific devices.  It doesn't mean that it's known to
be broken for these devices at all.  They should still work as is via
reset_resume invocation.


Takashi