All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] Move function declaration from C source to header file
Date: Sun, 01 Jun 2008 21:01:33 +0200	[thread overview]
Message-ID: <4842F20D.2070006@mail.berlios.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 154 bytes --]

This patch moves the declaration for function wav_start_capture from
C source to the header file.

Please apply the patch to Qemu trunk.

Thanks,
Stefan


[-- Attachment #2: audio.patch --]
[-- Type: text/x-diff, Size: 939 bytes --]

Index: audio/audio.h
===================================================================
--- audio/audio.h	(revision 4638)
+++ audio/audio.h	(working copy)
@@ -87,6 +87,9 @@
     uint64_t old_ts;
 } QEMUAudioTimeStamp;
 
+int wav_start_capture (CaptureState *s, const char *path, int freq,
+                       int bits, int nchannels);
+
 void AUD_vlog (const char *cap, const char *fmt, va_list ap);
 void AUD_log (const char *cap, const char *fmt, ...)
 #ifdef __GNUC__
Index: monitor.c
===================================================================
--- monitor.c	(revision 4638)
+++ monitor.c	(working copy)
@@ -1264,9 +1264,6 @@
 }
 
 #ifdef HAS_AUDIO
-int wav_start_capture (CaptureState *s, const char *path, int freq,
-                       int bits, int nchannels);
-
 static void do_wav_capture (const char *path,
                             int has_freq, int freq,
                             int has_bits, int bits,

             reply	other threads:[~2008-06-01 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 19:01 Stefan Weil [this message]
2008-06-03 18:53 ` [Qemu-devel] [PATCH] Move function declaration from C source to header file Anthony Liguori

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=4842F20D.2070006@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --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 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.