From: Erik Mouw <erik@harddisk-recovery.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2.6.0-test11] debug messages, ALSA or USB related
Date: Tue, 2 Dec 2003 15:54:41 +0100 [thread overview]
Message-ID: <20031202145441.GB28315@bitwizard.nl> (raw)
In-Reply-To: <s5h8ylve22q.wl@alsa2.suse.de>
On Tue, Dec 02, 2003 at 03:17:33PM +0100, Takashi Iwai wrote:
> At Tue, 2 Dec 2003 00:39:41 +0100,
> Erik Mouw wrote:
> >
> > At first glance it looks USB related, but it might as well be that the
> > ALSA code is the real culprit.
>
> yes, it's a known bug in ALSA's snd-usb-audio driver.
> it was already fixed on the recent version (1.0.0rc1).
OK. I suppose you'll push it to Linus/Andrew soonish?
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
| Data lost? Stay calm and contact Harddisk-recovery.com
next prev parent reply other threads:[~2003-12-02 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 23:39 [BUG 2.6.0-test11] debug messages, ALSA or USB related Erik Mouw
2003-12-02 14:17 ` Takashi Iwai
2003-12-02 14:54 ` Erik Mouw [this message]
2003-12-02 15:04 ` Takashi Iwai
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=20031202145441.GB28315@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--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;
as well as URLs for NNTP newsgroup(s).