From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: GCC-4 Patch for btsco
Date: Fri, 17 Jun 2005 13:05:18 +0200 [thread overview]
Message-ID: <1119006318.8980.126.camel@pegasus> (raw)
In-Reply-To: <loom.20050617T124909-183@post.gmane.org>
Hi Bastian,
> > > - Fix hci_switch_role expecting a bdaddr_t as the second argument (not a
> > > "bdaddr_t *")
> >
> > this was a bug in the earlier library versions. The correct argument is
> > a "bdaddr_t *" as for all other functions.
>
> I believe you mean that there was a bug in the headers. In which version of the
> bluez-libs was this fixed?
the bug was also present in the function itself. I have no idea how it
slipped into the source. I fixed it with the bluez-libs-2.11 release.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-06-17 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 10:05 [Bluez-devel] GCC-4 Patch for btsco Bastien Nocera
2005-06-17 10:23 ` Marcel Holtmann
2005-06-17 10:51 ` [Bluez-devel] " Bastien Nocera
2005-06-17 11:05 ` Marcel Holtmann [this message]
2005-06-17 11:33 ` Bastien Nocera
2005-06-17 13:31 ` Brad Midgley
2005-06-17 20:11 ` Bastien Nocera
2005-06-17 20:49 ` Brad Midgley
2005-06-17 21:26 ` Bastien Nocera
2005-06-17 18:45 ` Brad Midgley
2005-06-17 18:49 ` Luiz Fernando Capitulino
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=1119006318.8980.126.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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