From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Stefan Seyfried <seife@sphairon.com>
Subject: [PATCH 2/2] Add hack to allow compilation with old bluez lib
Date: Sun, 14 Feb 2010 12:33:32 +0100 [thread overview]
Message-ID: <1266147212-32461-3-git-send-email-stefan.seyfried@googlemail.com> (raw)
In-Reply-To: <1266147212-32461-2-git-send-email-stefan.seyfried@googlemail.com>
From: Stefan Seyfried <seife@sphairon.com>
---
parser/hci.c | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/parser/hci.c b/parser/hci.c
index e4fc473..33c3640 100644
--- a/parser/hci.c
+++ b/parser/hci.c
@@ -41,6 +41,12 @@
#include <bluetooth/hci.h>
#include <bluetooth/hci_lib.h>
+/* ugly hack, as hci.h changed incompatibly with bluez 4.61 */
+#ifndef OCF_READ_INQ_RESPONSE_TX_POWER_LEVEL
+#define OCF_READ_INQ_RESPONSE_TX_POWER_LEVEL OCF_READ_INQUIRY_TRANSMIT_POWER_LEVEL
+#define read_inq_response_tx_power_level_rp read_inquiry_transmit_power_level_rp
+#endif
+
#include "parser.h"
static uint16_t manufacturer = DEFAULT_COMPID;
--
1.6.6.1
next prev parent reply other threads:[~2010-02-14 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 11:33 [PATCH 0/2] Fix hcidump compilation with bluez-4.61+ Stefan Seyfried
2010-02-14 11:33 ` [PATCH 1/2] Fix compilation with bluez 4.61's changed hci.h Stefan Seyfried
2010-02-14 11:33 ` Stefan Seyfried [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-17 12:49 [Patch 0/2] Resend: Fix hcidump compilation with bluez-4.61+ Stefan Seyfried
2010-02-17 12:49 ` [PATCH 1/2] Fix compilation with bluez 4.61's changed hci.h Stefan Seyfried
2010-02-17 12:49 ` [PATCH 2/2] Add hack to allow compilation with old bluez lib Stefan Seyfried
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=1266147212-32461-3-git-send-email-stefan.seyfried@googlemail.com \
--to=stefan.seyfried@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=seife@sphairon.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;
as well as URLs for NNTP newsgroup(s).