From: Tim Renouf <tpr.vger@botech.co.uk>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bug and possible patch for dbus DiscoverServices
Date: Thu, 10 Jun 2010 21:20:23 +0100 [thread overview]
Message-ID: <20100610202023.GC16611@botech.co.uk> (raw)
In-Reply-To: <AANLkTinlsskks35CHsSlDueAGCi4HeicWjHLUTQcfzYC@mail.gmail.com>
On Thu, Jun 10, 2010 at 04:48:58PM +0300, Luiz Augusto von Dentz wrote:
> I would just rework it a bit to make the tmp_records to always store
> the last search, something like the following:
>
> - if (device->tmp_records && req->records) {
> + if (device->tmp_records)
> sdp_list_free(device->tmp_records,
> (sdp_free_func_t) sdp_record_free);
> - device->tmp_records = req->records;
> - req->records = NULL;
> - }
> +
> + device->tmp_records = req->records;
> + req->records = NULL;
>
> if (!req->profiles_added && !req->profiles_removed) {
> DBG("%s: No service update", device->path);
> @@ -1522,7 +1522,7 @@ send_reply:
>
> if (dbus_message_is_method_call(req->msg, DEVICE_INTERFACE,
> "DiscoverServices"))
> - discover_services_reply(req, err, req->records);
> + discover_services_reply(req, err, device->tmp_records);
> else if (dbus_message_is_method_call(req->msg, ADAPTER_INTERFACE,
> "CreatePairedDevice"))
> create_device_reply(device, req);
>
> What do you think?
Thanks, that looks good, I'll use that.
What is the procedure to get it included in future versions of BlueZ ?
Does someone sweep this list for patches to review and possibly
include ?
Thanks.
-tpr
next prev parent reply other threads:[~2010-06-10 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 12:58 bug and possible patch for dbus DiscoverServices Tim Renouf
2010-06-10 13:48 ` Luiz Augusto von Dentz
2010-06-10 20:20 ` Tim Renouf [this message]
2010-06-10 22:19 ` Luiz Augusto von Dentz
2010-06-11 9:41 ` Luiz Augusto von Dentz
2010-06-11 15:46 ` Johan Hedberg
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=20100610202023.GC16611@botech.co.uk \
--to=tpr.vger@botech.co.uk \
--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).