From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL for-1.7 0/1] audio bugfix
Date: Thu, 24 Oct 2013 15:41:49 +0200 [thread overview]
Message-ID: <1382622110-19460-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Single audio bugfix for 1.7.
please pull,
Gerd
The following changes since commit fc8ead74674b7129e8f31c2595c76658e5622197:
Merge remote-tracking branch 'qemu-kvm/uq/master' into staging (2013-10-18 10:03:24 -0700)
are available in the git repository at:
git://git.kraxel.org/qemu audio.2
for you to fetch changes up to b4350deed67b95651896ddb60cf9f765093a4848:
audio: honor QEMU_AUDIO_TIMER_PERIOD instead of waking up every *nano* second (2013-10-23 10:37:27 +0200)
----------------------------------------------------------------
Hans de Goede (1):
audio: honor QEMU_AUDIO_TIMER_PERIOD instead of waking up every *nano* second
audio/audio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2013-10-24 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 13:41 Gerd Hoffmann [this message]
2013-10-24 13:41 ` [Qemu-devel] [PATCH 1/1] audio: honor QEMU_AUDIO_TIMER_PERIOD instead of waking up every *nano* second Gerd Hoffmann
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=1382622110-19460-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).