From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [RFC v0 4/5] adapter: add RequestDiscoverable() and ReleaseDiscoverable()
Date: Thu, 6 Jun 2013 22:50:32 +0700 [thread overview]
Message-ID: <CABBYNZLxeRNBL4KBjs624pVSvDv76pbV4u+Y8K6VuNnHD8ApVg@mail.gmail.com> (raw)
In-Reply-To: <1370528339-7921-4-git-send-email-gustavo@padovan.org>
Hi Gustavo,
On Thu, Jun 6, 2013 at 9:18 PM, Gustavo Padovan <gustavo@padovan.org> wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> With those two methods BlueZ is now aware of client lifetime and can set
> Discoverable back to False if all clients exit or call
> ReleaseDiscoverable()
> ---
This probably should be handled int the component controlling the
powered state like we used to have with RequestSession or we can have
an agent to the power/policy manager asking if it is ok to power on
the adapter.
next prev parent reply other threads:[~2013-06-06 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 14:18 [RFC v0 1/5] adapter: rename discovery_client to watch_client Gustavo Padovan
2013-06-06 14:18 ` [RFC v0 2/5] adapter: rename compare_discovery_sender Gustavo Padovan
2013-06-06 14:18 ` [RFC v0 3/5] doc: add RequestDiscoverable() and ReleaseDiscoverable() Gustavo Padovan
2013-06-06 14:18 ` [RFC v0 4/5] adapter: " Gustavo Padovan
2013-06-06 15:50 ` Luiz Augusto von Dentz [this message]
2013-06-06 15:59 ` Gustavo Padovan
2013-06-06 16:06 ` Luiz Augusto von Dentz
2013-06-06 16:20 ` Gustavo Padovan
2013-06-07 7:58 ` Mikel Astiz
2013-06-06 14:18 ` [RFC v0 5/5] test: add requestdiscoverable command to test-adapter Gustavo Padovan
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=CABBYNZLxeRNBL4KBjs624pVSvDv76pbV4u+Y8K6VuNnHD8ApVg@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.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).