All of lore.kernel.org
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Subject: Re: [PATCH 00/14] neard plugin update
Date: Mon, 11 Feb 2013 10:52:36 +0100	[thread overview]
Message-ID: <2589959.gQ4yNVdaLa@uw000953> (raw)
In-Reply-To: <1360224844-12280-1-git-send-email-szymon.janc@tieto.com>

Hi All,

On Thursday 07 of February 2013 10:13:50 Janc Szymon wrote:
> This set adds some new features to neard plugin to match it with
> recent changes in neard daemon:
> - support for carrier power state hint (already merged)
> - update register API [with fallback to legacy support] (pending review)

Just to notify that register API changes were just merged into neard.git so all
code needed is now present in neard daemon.

> 
> Power state hint could be use to improve IOP e.g. delay or retry pairing when
> remote device in activating or incative state.
> 
> Other than that bugfixes, small improvements and some code refactoring to
> make it better prepared for future feature addition e.g. to perform more
> action on PushOOB than only pairing.
> 
> There are still some open points regarding how to properly map adapter
> state (powered/pairable/connectable) to carrier power state but those
> could be discussed separately later on.
> 
> Comments are welcome.
> 
> BR
> Szymon Janc
> 
> Ravi kumar Veeramally (1):
>   neard: Updated neard handover registration agent api calls.
> 
> Szymon Janc (13):
>   neard: Adjust errors to latest API changes
>   neard: Refactor message processing
>   neard: Add ability to parse 'State' field
>   neard: Move pairable check from check_adapter
>   adapter: Add btd_adapter_get_powered function
>   neard: Check if adapter is powered in PushOOB
>   adapter: Add btd_adapter_get_connectable function
>   neard: Add support for setting power state in RequestOOB reply
>   neard: Use path instead of boolean to track if registered to neard
>   neard: Restrict method calls only to neard process
>   neard: Use bool instead of gboolean for agent_register_postpone
>   neard: Update copyright information
>   neard: Add fallback to legacy register if register failed
> 
>  plugins/neard.c | 562 ++++++++++++++++++++++++++++++++++----------------------
>  src/adapter.c   |  16 ++
>  src/adapter.h   |   2 +
>  3 files changed, 361 insertions(+), 219 deletions(-)
> 
> 

      parent reply	other threads:[~2013-02-11  9:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07  8:13 [PATCH 00/14] neard plugin update Szymon Janc
2013-02-07  8:13 ` [PATCH 01/14] neard: Adjust errors to latest API changes Szymon Janc
2013-02-07  8:13 ` [PATCH 02/14] neard: Refactor message processing Szymon Janc
2013-02-07  8:13 ` [PATCH 03/14] neard: Add ability to parse 'State' field Szymon Janc
2013-02-07  8:13 ` [PATCH 04/14] neard: Move pairable check from check_adapter Szymon Janc
2013-02-07  8:13 ` [PATCH 05/14] adapter: Add btd_adapter_get_powered function Szymon Janc
2013-02-07  8:13 ` [PATCH 06/14] neard: Check if adapter is powered in PushOOB Szymon Janc
2013-02-07  8:13 ` [PATCH 07/14] adapter: Add btd_adapter_get_connectable function Szymon Janc
2013-02-07  8:13 ` [PATCH 08/14] neard: Add support for setting power state in RequestOOB reply Szymon Janc
2013-02-07  8:13 ` [PATCH 09/14] neard: Use path instead of boolean to track if registered to neard Szymon Janc
2013-02-15  8:46   ` Johan Hedberg
2013-02-07  8:14 ` [PATCH 10/14] neard: Restrict method calls only to neard process Szymon Janc
2013-02-07  8:14 ` [PATCH 11/14] neard: Use bool instead of gboolean for agent_register_postpone Szymon Janc
2013-02-07  8:14 ` [PATCH 12/14] neard: Update copyright information Szymon Janc
2013-02-07  8:14 ` [PATCH 13/14] neard: Updated neard handover registration agent api calls Szymon Janc
2013-02-07  8:14 ` [PATCH 14/14] neard: Add fallback to legacy register if register failed Szymon Janc
2013-02-11  9:52 ` Szymon Janc [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=2589959.gQ4yNVdaLa@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ravikumar.veeramally@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.