public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	alsa-devel@lists.sourceforge.net, juhl-lkml@dif.dk
Subject: Re: ALSA Oops (triggered by xmms)
Date: Fri, 15 Apr 2005 16:54:11 +0200	[thread overview]
Message-ID: <425FD593.7080402@g-house.de> (raw)
In-Reply-To: <s5hbr8ge7yi.wl@alsa2.suse.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Takashi Iwai wrote:
> 
> Also, the latest CVS alsa-lib checks the timer protocol version to
> avoid this Oops with the older kenel.  1.0.9-rc3 is planned to be
> released soon, so wait for a moment...

um, i'll wait for the next release as i don't track alsa-cvs. but i do
track 2.6-BK (again) and the oops is gone ;-)


Jesper Juhl wrote:
>> yeah, but the oops doesn't wrap at 80 chars itsself and often oopses
>> are hardly readable inline.
>
> I would still suggest including the info inline and then if you think
> it's needed /also/ provide the link you did - then you've covered all
> bases :)

will do, next time 8-)


thanks to all involved for all your replies,
Christian.
- --
BOFH excuse #388:

Bad user karma.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCX9WT+A7rjkF8z0wRAlp2AJ0doKLm4OsK2i8nNx6uezrcfPF15QCeNkuO
eVCEuP0U5LrUOToHXEb6cBs=
=Feow
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-04-15 14:54 UTC|newest]

Thread overview: 9+ 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
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 [this message]
     [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=425FD593.7080402@g-house.de \
    --to=evil@g-house.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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