Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Matija Nalis <mnalis-alsadev@voyager.hr>
Cc: alsa-devel@alsa-project.org
Subject: Re: cmipci and sound skipping ?
Date: Tue, 23 Mar 2010 09:36:01 +0100	[thread overview]
Message-ID: <4BA87D71.2010505@ladisch.de> (raw)
In-Reply-To: <20100315193557.GA3884@eagle102.home.lan>

Matija Nalis wrote:
> On Mon, Mar 15, 2010 at 01:17:20PM +0100, Clemens Ladisch wrote:
> > Please try the patch below.
> 
> Thanks Clemens, that patch seems to have fixed it !

Are you okay with your email address (which one?) to be published with
the patch:
  Reported-and-tested-by: Matija Nalis <...>


Regards,
Clemens

  reply	other threads:[~2010-03-23  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-13 20:11 cmipci and sound skipping ? Matija Nalis
2010-03-15 12:17 ` Clemens Ladisch
2010-03-15 19:35   ` Matija Nalis
2010-03-23  8:36     ` Clemens Ladisch [this message]
     [not found]       ` <20100323201749.GA4675@eagle102.home.lan>
2010-03-24  6:57         ` Clemens Ladisch

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=4BA87D71.2010505@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=mnalis-alsadev@voyager.hr \
    /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