public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Mike <puffy.taco@gmail.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: reverse SDP issue
Date: Mon, 19 Mar 2012 20:04:36 -0300	[thread overview]
Message-ID: <20120319230436.GA27304@x220> (raw)
In-Reply-To: <CAB7rCTg4YLsE7uNbR8mRH_cubtMmBnTZUnJ3U4vL_AsyjA7xzA@mail.gmail.com>

Hi Mike,

On Mon, Mar 19, 2012, Mike wrote:
> I notice a change in commit d2920be715974795b51f9cc3279947104da3647b
> [1] that changes the "reverse" variable for an SDP query:
> 
>  -       device_browse_sdp(device, NULL, NULL, NULL, TRUE);
> +       if (device_is_bredr(device))
> +               device_browse_sdp(device, NULL, NULL, NULL, FALSE);
> +       else
> +               device_browse_primary(device, NULL, NULL, FALSE);
> 
> You can see the original had reverse as TRUE, but the patch may have
> inadvertently changed it to FALSE..kernel.org/majordomo-info.html

That looks like a definitive bug. Good that you caught it. Vinicius
(author of the commit) care to comment?

As for the partial service removal changes to the device driver API, it
looks pretty messy to me. Is there any reason why we couldn't just
restrict calling remove() for when removing the entire device object
(and never call it when doing subsequent service discoveries)?

Johan

  parent reply	other threads:[~2012-03-19 23:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 22:19 reverse SDP issue Mike
2012-03-19 22:36 ` Mike
2012-03-19 23:04 ` Johan Hedberg [this message]
2012-03-20 17:35   ` Vinicius Costa Gomes
2012-03-20 18:27     ` Mike
2012-03-20 18:39       ` Mike
2012-03-20 19:21         ` Mike
2012-03-20 20:18           ` Mike
2012-03-21 12:45     ` Johan Hedberg
2012-03-21 13:11       ` Query on attribute api service object path Jaganath
2012-03-21 14:18         ` Anderson Lizardo
2012-03-21 14:27           ` Jaganath

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=20120319230436.GA27304@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=puffy.taco@gmail.com \
    /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