From: Pacho Ramos <pacho@gentoo.org>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluetooth.h: fix compile issue when using in C++
Date: Wed, 01 Aug 2012 16:41:33 +0200 [thread overview]
Message-ID: <1343832093.2121.0.camel@belkin4> (raw)
In-Reply-To: <1343548354.25518.1.camel@belkin4>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
El dom, 29-07-2012 a las 09:52 +0200, Pacho Ramos escribió:
> Hello
>
> Today I got a report downstream showing that old problem:
> http://permalink.gmane.org/gmane.linux.bluez.kernel/22306
>
> is still not fixed.
>
> Could you please commit debian patch to fix this?
> http://patch-tracker.debian.org/patch/series/view/bluez/4.101-1/09_fix_ftbfs_with_c99.patch
>
> Thanks a lot
Any news about this? Thanks
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-08-01 14:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 7:52 bluetooth.h: fix compile issue when using in C++ Pacho Ramos
2012-08-01 14:41 ` Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-16 10:11 [PATCH] " Patrick Ohly
2012-03-04 23:27 ` Marcel Holtmann
2012-03-05 7:33 ` Patrick Ohly
[not found] ` <CAOcK=CNZofxZtUp4Zh5eiGMM_TYrbGOwseA3tcwAnAFDvLEFxg@mail.gmail.com>
2012-03-05 13:12 ` Patrick Ohly
2012-03-05 14:53 ` Markus Rathgeb
2012-07-27 16:38 ` W. Trevor King
2012-08-17 5:18 ` W. Trevor King
2012-08-27 23:40 ` Johan Hedberg
2012-09-05 17:27 ` Pacho Ramos
2012-09-05 17:56 ` Pacho Ramos
2012-03-05 20:06 ` Lucas De Marchi
2012-03-08 13:22 ` Markus Rathgeb
2012-03-08 17:51 ` Marcel Holtmann
2012-03-08 20:59 ` Markus Rathgeb
2012-03-09 10:52 ` Markus Rathgeb
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=1343832093.2121.0.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=linux-bluetooth@vger.kernel.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).