From: Ondrej Zary <linux@rainbow-software.org>
To: Jesper Juhl <jj@chaosbits.net>
Cc: "Benny Sjöstrand" <benny@hostmobility.com>,
linux-kernel@vger.kernel.org, "Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.de>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] cs46xx memory management fixes for cs46xx_dsp_spos_create() - make sure we free and don't do pointless work.
Date: Sun, 31 Oct 2010 18:29:10 +0100 [thread overview]
Message-ID: <201010311829.13924.linux@rainbow-software.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1010302143530.1572@swampdragon.chaosbits.net>
On Saturday 30 October 2010 21:44:33 Jesper Juhl wrote:
> On Sat, 30 Oct 2010, Ondrej Zary wrote:
> > On Saturday 30 October 2010 00:18:57 Benny Sjöstrand wrote:
> > > Hello again!
> > >
> > > Just doing a reply-all.
> > > It's has been many years since I did anything to the cs46xx driver, so
> > > I'm wondering
> > > if there's anyone out there still using a cs46xx sound card?
> > > I think the changes look's correct, but I can't test it, I do not have
> > > a cs46xx hardware anymore.
> >
> > Sure, there are many of these cards "out there". I just got a "new"
> > Terratec DMX Xfire 1024 (CS4624). I'll test the patch.
>
> Thanks a lot. Let me know how the test goes :-)
It works fine. Playing music right now.
--
Ondrej Zary
next prev parent reply other threads:[~2010-10-31 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 20:54 [PATCH] cs46xx memory management fixes for cs46xx_dsp_spos_create() - make sure we free and don't do pointless work Jesper Juhl
2010-10-29 22:18 ` Benny Sjöstrand
2010-10-30 12:06 ` Ondrej Zary
2010-10-30 19:44 ` Jesper Juhl
2010-10-31 17:29 ` Ondrej Zary [this message]
2010-11-01 9:38 ` Takashi Iwai
2010-11-01 18:23 ` Jesper Juhl
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=201010311829.13924.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=alsa-devel@alsa-project.org \
--cc=benny@hostmobility.com \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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).