Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: "MONTANARO Luciano (MM)" <luciano.montanaro@magnetimarelli.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] Wrap hw_ptr to boundary in pcm_ioplug
Date: Tue, 04 Mar 2014 13:03:26 +0100	[thread overview]
Message-ID: <5315C10E.2010502@perex.cz> (raw)
In-Reply-To: <67BA5DEFFBE7BF46B4C53F7E5FC5AD44344700ED7C@MXCL13.fgremc.it>

Date 4.3.2014 12:51, MONTANARO Luciano (MM) wrote:
> The function snd_pcm_ioplug_hw_ptr_update() always increased the hw_ptr
> by delta, without wrapping it to the boundary. This would lead to
> problems when after many hours, the hw_ptr would overflow.

Applied to our GIT tree. Thanks.

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.

      reply	other threads:[~2014-03-04 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 11:51 [PATCH] Wrap hw_ptr to boundary in pcm_ioplug MONTANARO Luciano (MM)
2014-03-04 12:03 ` Jaroslav Kysela [this message]

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=5315C10E.2010502@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=luciano.montanaro@magnetimarelli.com \
    /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