From: Lee Revell <rlrevell@joe-job.com>
To: Christian Kujau <evil@g-house.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
alsa-devel@lists.sourceforge.net
Subject: Re: ALSA Oops (triggered by xmms)
Date: Thu, 14 Apr 2005 19:35:19 -0400 [thread overview]
Message-ID: <1113521720.19830.35.camel@mindpipe> (raw)
In-Reply-To: <425EFB32.2010000@g-house.de>
On Fri, 2005-04-15 at 01:22 +0200, Christian Kujau wrote:
> maybe some guru can shed some light on what's going on in xmms-oops.txt
> and tell me who's to bug here :->
Fixed in 2.6.11.7.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
WARNING: multiple messages have this Message-ID (diff)
From: Lee Revell <rlrevell@joe-job.com>
To: Christian Kujau <evil@g-house.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
alsa-devel@lists.sourceforge.net
Subject: Re: ALSA Oops (triggered by xmms)
Date: Thu, 14 Apr 2005 19:35:19 -0400 [thread overview]
Message-ID: <1113521720.19830.35.camel@mindpipe> (raw)
In-Reply-To: <425EFB32.2010000@g-house.de>
On Fri, 2005-04-15 at 01:22 +0200, Christian Kujau wrote:
> maybe some guru can shed some light on what's going on in xmms-oops.txt
> and tell me who's to bug here :->
Fixed in 2.6.11.7.
Lee
next prev parent reply other threads:[~2005-04-14 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 23:22 ALSA Oops (triggered by xmms) Christian Kujau
2005-04-14 23:35 ` Lee Revell [this message]
2005-04-14 23:35 ` Lee Revell
2005-04-15 0:16 ` Christian Kujau
2005-04-15 0:21 ` Lee Revell
2005-04-15 8:54 ` [Alsa-devel] " Takashi Iwai
2005-04-15 14:54 ` Christian Kujau
[not found] ` <Pine.LNX.4.62.0504150150240.3466@dragon.hyggekrogen.localhost>
2005-04-15 0:15 ` Christian Kujau
2005-04-15 0:29 ` Jesper Juhl
2005-04-15 8:19 ` Daniel Drake
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=1113521720.19830.35.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=evil@g-house.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.