From: "Christian O. Andersson" <christian.o.andersson@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: hci_read_remote_name_with_clock_offset vs hci_read_remote_name
Date: Wed, 24 Sep 2008 11:55:00 +0200 [thread overview]
Message-ID: <1222250100.13534.10.camel@ludwig-van> (raw)
Hey guys,
Please bare with me as I'm just starting to learn the concepts of
hci-traffic. I hope this is the right place to ask.
I was wondering - is there any performance gain in preferring
'hci_read_remote_name_with_clock_offset' to 'hci_read_remote_name' if
you already know the clock offset (from a previous inquiry).
Looking at the source code it seems as though the latter only calls the
former with the clock offset set to 0?
/Christian
reply other threads:[~2008-09-24 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1222250100.13534.10.camel@ludwig-van \
--to=christian.o.andersson@gmail.com \
--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