* non functionable snd-ad1816a in Kernel 2.6.18-rc2
@ 2006-07-18 9:34 Uwe Bugla
2006-07-24 19:40 ` Bjorn Helgaas
0 siblings, 1 reply; 4+ messages in thread
From: Uwe Bugla @ 2006-07-18 9:34 UTC (permalink / raw)
Cc: castet.matthieu, bjorn.helgaas, linux-acpi, len.brown, akpm,
ambx1
Hi everybody,
Just a reminder for everybody listening:
My soundcard (snd-ad1816a) does not work in Kernel 2.6.18-rc2.
I guess the reason for this is that Matthieu´s material is still residing in the mm-branch. Can I please have a constructive feedback where things are hanging after all that immense amount of time I spent to forward this issue?
A thousands of thanks for Matthieu´s work one more time!
The bug ID is 6292, and the ACPI_PRODUCER reject patch is still missing in the main vanilla tree.
Regards
Uwe
--
Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: non functionable snd-ad1816a in Kernel 2.6.18-rc2
2006-07-18 9:34 non functionable snd-ad1816a in Kernel 2.6.18-rc2 Uwe Bugla
@ 2006-07-24 19:40 ` Bjorn Helgaas
2006-07-27 13:45 ` Uwe Bugla
0 siblings, 1 reply; 4+ messages in thread
From: Bjorn Helgaas @ 2006-07-24 19:40 UTC (permalink / raw)
To: Uwe Bugla; +Cc: akpm, castet.matthieu, linux-acpi, len.brown, ambx1
On Tuesday 18 July 2006 03:34, Uwe Bugla wrote:
> Just a reminder for everybody listening:
> My soundcard (snd-ad1816a) does not work in Kernel 2.6.18-rc2.
> I guess the reason for this is that Matthieu´s material is still residing in the mm-branch. Can I please have a constructive feedback where things are hanging after all that immense amount of time I spent to forward this issue?
> A thousands of thanks for Matthieu´s work one more time!
> The bug ID is 6292, and the ACPI_PRODUCER reject patch is still missing in the main vanilla tree.
Yup, the patch is in the -mm tree, and should make its way to
the mainline vanilla kernel eventually. It does take a while,
because we want to make sure it doesn't break somebody else's
system while fixing yours.
Bjorn
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Re: non functionable snd-ad1816a in Kernel 2.6.18-rc2
2006-07-24 19:40 ` Bjorn Helgaas
@ 2006-07-27 13:45 ` Uwe Bugla
2006-07-27 15:11 ` Bjorn Helgaas
0 siblings, 1 reply; 4+ messages in thread
From: Uwe Bugla @ 2006-07-27 13:45 UTC (permalink / raw)
To: Bjorn Helgaas; +Cc: ambx1, len.brown, linux-acpi, castet.matthieu, akpm
-------- Original-Nachricht --------
Datum: Mon, 24 Jul 2006 13:40:56 -0600
Von: Bjorn Helgaas <bjorn.helgaas@hp.com>
An: "Uwe Bugla" <uwe.bugla@gmx.de>
Betreff: Re: non functionable snd-ad1816a in Kernel 2.6.18-rc2
> On Tuesday 18 July 2006 03:34, Uwe Bugla wrote:
> > Just a reminder for everybody listening:
> > My soundcard (snd-ad1816a) does not work in Kernel 2.6.18-rc2.
> > I guess the reason for this is that Matthieu´s material is still
> residing in the mm-branch. Can I please have a constructive feedback where things
> are hanging after all that immense amount of time I spent to forward this
> issue?
> > A thousands of thanks for Matthieu´s work one more time!
> > The bug ID is 6292, and the ACPI_PRODUCER reject patch is still missing
> in the main vanilla tree.
>
> Yup, the patch is in the -mm tree, and should make its way to
> the mainline vanilla kernel eventually. It does take a while,
> because we want to make sure it doesn't break somebody else's
> system while fixing yours.
>
> Bjorn
>
>
OK so far.
But how can we make sure that it does not break somebody else´s system while fixing mine when anything deriving from the two Intel guys is NAK?
If they would be a bit more cooperative things would go forward much faster I think.
I see this patchwork getting rusty in the mm-tree, and that can´t be it, can it?
Regards
Uwe
--
Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit!
"Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: non functionable snd-ad1816a in Kernel 2.6.18-rc2
2006-07-27 13:45 ` Uwe Bugla
@ 2006-07-27 15:11 ` Bjorn Helgaas
0 siblings, 0 replies; 4+ messages in thread
From: Bjorn Helgaas @ 2006-07-27 15:11 UTC (permalink / raw)
To: Uwe Bugla; +Cc: ambx1, len.brown, linux-acpi, castet.matthieu, akpm
On Thursday 27 July 2006 07:45, Uwe Bugla wrote:
> But how can we make sure that it does not break somebody
> else´s system while fixing mine when anything deriving
> from the two Intel guys is NAK?
I don't understand. The idea is that people will test
the -mm kernel and report any problems.
> If they would be a bit more cooperative things would go
> forward much faster I think.
I think it's going about the right pace. Usually things
stay in -mm for at least a month before we think about
putting them upstream. And of course we don't push minor
bugfixes upstream when we're close to an upstream release.
Bjorn
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-07-27 15:11 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-18 9:34 non functionable snd-ad1816a in Kernel 2.6.18-rc2 Uwe Bugla
2006-07-24 19:40 ` Bjorn Helgaas
2006-07-27 13:45 ` Uwe Bugla
2006-07-27 15:11 ` Bjorn Helgaas
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox