mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Fubo Chen <fubo.chen@gmail.com>
Cc: "Niccolò Belli" <darkbasic@linuxsystems.it>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf
Date: Sun, 11 May 2014 11:51:51 +0200	[thread overview]
Message-ID: <s5h4n0wod6w.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAJAFBLBjW3v_qmOiU+0V2AuwgOV2bXRGdZtpUAoDDJuq0ZtEKQ@mail.gmail.com>

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

  reply	other threads:[~2014-05-11  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  8:49 Fubo Chen
2014-05-11  9:51 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-08 14:06 Niccolò Belli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h4n0wod6w.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=darkbasic@linuxsystems.it \
    --cc=fubo.chen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®