* Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf
@ 2014-05-08 14:06 Niccolò Belli
0 siblings, 0 replies; 3+ messages in thread
From: Niccolò Belli @ 2014-05-08 14:06 UTC (permalink / raw)
To: linux-kernel
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.
Thanks,
Niccolò
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf
2014-05-11 8:49 Fubo Chen
@ 2014-05-11 9:51 ` Takashi Iwai
0 siblings, 0 replies; 3+ messages in thread
From: Takashi Iwai @ 2014-05-11 9:51 UTC (permalink / raw)
To: Fubo Chen; +Cc: Niccolò Belli, Linux Kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf
@ 2014-05-11 8:49 Fubo Chen
2014-05-11 9:51 ` Takashi Iwai
0 siblings, 1 reply; 3+ messages in thread
From: Fubo Chen @ 2014-05-11 8:49 UTC (permalink / raw)
To: Niccolò Belli; +Cc: Linux Kernel, Takashi Iwai
(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.
>
> Thanks,
> Niccolò
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-11 9:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-08 14:06 Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf Niccolò Belli
2014-05-11 8:49 Fubo Chen
2014-05-11 9:51 ` Takashi Iwai
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome