qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 1/7] clean build: Add bt_host_hci prototype
Date: Sun, 08 Mar 2009 15:56:12 +0100	[thread overview]
Message-ID: <49B3DC8C.6050700@web.de> (raw)
In-Reply-To: <20090221190055.12485.61603.stgit@mchn012c.ww002.siemens.net>

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

Jan Kiszka wrote:
> Silence compiler warning by providing a prototype in the CONFIG_BLUEZ
> case (hw/bt.h provides it otherwise).
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
>  bt-host.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/bt-host.c b/bt-host.c
> index 07679f6..066757a 100644
> --- a/bt-host.c
> +++ b/bt-host.c
> @@ -31,6 +31,8 @@
>  #  include <bluetooth/bluetooth.h>
>  #  include <bluetooth/hci.h>
>  #  include <bluetooth/hci_lib.h>
> +/* Silence compiler warning */
> +struct HCIInfo *bt_host_hci(const char *id);
>  # else
>  #  include "hw/bt.h"
>  #  define HCI_MAX_FRAME_SIZE	1028

Thanks for applying the other patches, but this tiny one always seems to
be ignored - for unknown reasons. :)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-03-08 14:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 19:00 [Qemu-devel] [PATCH 0/7] clean build - eliminate warnings Jan Kiszka
2009-02-21 19:00 ` [Qemu-devel] [PATCH 1/7] clean build: Add bt_host_hci prototype Jan Kiszka
2009-03-08 14:56   ` Jan Kiszka [this message]
2009-03-08 18:44     ` [Qemu-devel] " Aurelien Jarno
2009-03-08 19:56       ` [Qemu-devel] [PATCH] clean build: Add bt-host.h Jan Kiszka
2009-03-10 21:43         ` Aurelien Jarno
2009-03-10 23:03         ` andrzej zaborowski
2009-03-11  9:02           ` [Qemu-devel] " Jan Kiszka
2009-03-20 14:51             ` andrzej zaborowski
2009-02-21 19:00 ` [Qemu-devel] [PATCH 5/7] clean build: Fix remaining cris warnings Jan Kiszka
2009-02-21 23:03   ` Stuart Brady
2009-02-21 23:12     ` Stuart Brady
2009-02-21 23:13     ` Laurent Desnogues
2009-02-22 10:36       ` [Qemu-devel] [PATCH v2 " Jan Kiszka
2009-02-22 14:14         ` Edgar E. Iglesias
2009-02-21 23:14     ` [Qemu-devel] [PATCH " Paul Brook
2009-02-21 19:00 ` [Qemu-devel] [PATCH 4/7] clean build: Fix arm build warnings Jan Kiszka
2009-03-07 21:48   ` Aurelien Jarno
2009-02-21 19:00 ` [Qemu-devel] [PATCH 3/7] arm: Fix gic_irq_state.level bitfield type Jan Kiszka
2009-03-07 21:48   ` Aurelien Jarno
2009-02-21 19:00 ` [Qemu-devel] [PATCH 2/7] clean build: Fix irq_info and pic_info related warnings Jan Kiszka
2009-02-21 19:00 ` [Qemu-devel] [PATCH 6/7] clean build: Fix remaining m68k warnings Jan Kiszka
2009-03-07 21:48   ` Aurelien Jarno
2009-02-21 19:00 ` [Qemu-devel] [PATCH 7/7] clean build: Fix remaining sh4 warnings Jan Kiszka
2009-02-21 19:43 ` [Qemu-devel] [PATCH 0/7] clean build - eliminate warnings Laurent Desnogues
2009-02-21 20:09   ` [Qemu-devel] " Jan Kiszka
2009-02-21 23:08     ` Laurent Desnogues
2009-02-22 10:39       ` Jan Kiszka
2009-02-22 11:09         ` Jan Kiszka
2009-02-22  0:59     ` Edgar E. Iglesias
2009-02-22 10:20       ` Jan Kiszka

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=49B3DC8C.6050700@web.de \
    --to=jan.kiszka@web.de \
    --cc=aurelien@aurel32.net \
    --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).