public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [sound] mpd loops on current -next
Date: Sat, 06 Jun 2009 18:56:04 +0200	[thread overview]
Message-ID: <4A2A9FA4.8000007@gmail.com> (raw)
In-Reply-To: <s5heitx8gjs.wl%tiwai@suse.de>

On 06/06/2009 06:37 PM, Takashi Iwai wrote:
>>> I found a regression in current -next caused by
>>> c44941e05900fe85f6091456f9e313b446a97ae9
>>> (PCM midlevel: Do not update hw_ptr_jiffies when hw_ptr is not changed)
>>
>> Oops. It seems like typo. Could you try this patch, please?
> 
> Ah, that's the cause of the bug with PA on the recent driver.
> I didn't experience the problem because I myself don't use PA :)

FWIW me neither...

  reply	other threads:[~2009-06-06 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-06 15:46 [sound] mpd loops on current -next Jiri Slaby
2009-06-06 15:52 ` Jaroslav Kysela
2009-06-06 15:58   ` Jiri Slaby
2009-06-06 16:37   ` Takashi Iwai
2009-06-06 16:56     ` Jiri Slaby [this message]
2009-06-07 10:28     ` 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=4A2A9FA4.8000007@gmail.com \
    --to=jirislaby@gmail.com \
    --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