From: Marcel Holtmann <marcel@holtmann.org>
To: Olivier Le Pogam <olepogam@free.fr>,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluez libs 3.22 & hci_read_remote_name
Date: Wed, 07 Nov 2007 19:28:21 +0100 [thread overview]
Message-ID: <1194460101.4635.3.camel@aeonflux> (raw)
In-Reply-To: <00ef01c8214f$1f9cc580$0200a8c0@jester>
Hi Olivier,
> I have big problems making "hci_read_remote_name" work using libs 3.22, it
> is very long or blocking.
I have seen that issue, too. However right now, I don't know what is
wrong with the code. It looks good to me. Must be some obvious thinko.
> I had to roll back to 3.20 which is working fine.
The 3.21 should be fine, too.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-11-07 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 11:14 [Bluez-devel] Bluez utils and libs 3.22 Pierre Savary
2007-11-07 15:01 ` [Bluez-devel] Bluez libs 3.22 & hci_read_remote_name Olivier Le Pogam
2007-11-07 18:26 ` Manuel Naranjo
2007-11-07 18:28 ` Marcel Holtmann [this message]
2007-11-07 18:27 ` [Bluez-users] [Bluez-devel] Bluez utils and libs 3.22 Marcel Holtmann
2007-11-08 7:49 ` [Bluez-devel] [Bluez-users] " Pierre Savary
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=1194460101.4635.3.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=olepogam@free.fr \
/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