From: Lennart Poettering <mznyfn@0pointer.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] PulseAudio plugin: report XRUN state back to application
Date: Sat, 22 Dec 2007 23:34:00 +0100 [thread overview]
Message-ID: <20071222223359.GA13486@tango.0pointer.de> (raw)
In-Reply-To: <s5hd4txs49u.wl%tiwai@suse.de>
On Mon, 26.11.07 11:13, Takashi Iwai (tiwai@suse.de) wrote:
> > Alternatively, ioplug could be beefed up to properly handle XRUNs, but
> > I thought this fix is simpler.
>
> But it's a layer violation :)
>
> We need a proper state-notification function. It'd be simply setting
> the state in the end, but at least, it's clear and the ioplug can do
> any action or sanity-check if once needed.
>
> A proposed patch is below. Comments?
Looks good to me.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
prev parent reply other threads:[~2007-12-22 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 21:12 [PATCH] PulseAudio plugin: report XRUN state back to application Lennart Poettering
2007-11-26 10:13 ` Takashi Iwai
2007-12-22 22:34 ` Lennart Poettering [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=20071222223359.GA13486@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.