linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulisses Furquim <ulisses@profusion.mobi>
To: Andre Guedes <andre.guedes@openbossa.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [RFC v2 0/4] MGMT Start Discovery interleaved support
Date: Sun, 19 Feb 2012 10:13:09 -0300	[thread overview]
Message-ID: <CAA37ikbuWrH96UzspMz10QiumfuD+wyJ1BozJ0=HGWFN_8ayNg@mail.gmail.com> (raw)
In-Reply-To: <20120219105126.GA27110@x220.P-661HNU-F1>

Hi Johan,

On Sun, Feb 19, 2012 at 7:51 AM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> Hi Andre,
>
> On Fri, Feb 17, 2012, Andre Guedes wrote:
>> This RFCv2 series implements Marcel's and Johan's comments from previous
>> version. The changes are:
>> 1. Use MGMT_ADDR_* macros instead of hard-coded values to define discovery
>> type macros;
>> 2. Fix locking in mgmt_interleaved_discovery
>>
>> Marcel, I removed your ack from patch 1/4 because I changed it a little
>> bit. MGMT_ADDR_* macros were moved to hci_core.h since they are needed to
>> define discovery type macros.
>
> All four patches have been applied to my bluetooth-next tree. Thanks.
>
> I'd still like to have consistency in the locking since now your
> function is the only one handling the hdev lock by itself and that's
> something that can easily cause bugs in the long run. I.e. probably all
> mgmt_* functions should be converted to take hdev unlocked and handle
> the locking by themselves.

Do you think such a change is worth? I'm not sure if we have just one
function that deals with locking on its own.

Regards,

-- 
Ulisses Furquim
ProFUSION embedded systems
http://profusion.mobi
Mobile: +55 19 9250 0942
Skype: ulissesffs

      reply	other threads:[~2012-02-19 13:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17 23:39 [RFC v2 0/4] MGMT Start Discovery interleaved support Andre Guedes
2012-02-17 23:39 ` [RFC v2 1/4] Bluetooth: Prepare start_discovery Andre Guedes
2012-02-18  6:39   ` Marcel Holtmann
2012-02-17 23:39 ` [RFC v2 2/4] Bluetooth: Track discovery type Andre Guedes
2012-02-17 23:39 ` [RFC v2 3/4] Bluetooth: Merge INQUIRY and LE_SCAN discovery states Andre Guedes
2012-02-17 23:39 ` [RFC v2 4/4] Bluetooth: Interleaved discovery support Andre Guedes
2012-02-19 10:51 ` [RFC v2 0/4] MGMT Start Discovery interleaved support Johan Hedberg
2012-02-19 13:13   ` Ulisses Furquim [this message]

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='CAA37ikbuWrH96UzspMz10QiumfuD+wyJ1BozJ0=HGWFN_8ayNg@mail.gmail.com' \
    --to=ulisses@profusion.mobi \
    --cc=andre.guedes@openbossa.org \
    --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).