linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Alex Deymo <deymo@chromium.org>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	keybuk@chromium.org
Subject: Re: [PATCH v5 0/8] Autopair
Date: Fri, 10 May 2013 10:39:59 +0300	[thread overview]
Message-ID: <20130510073959.GA32047@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1368059882-9986-1-git-send-email-deymo@chromium.org>

Hi Alex,

On Wed, May 08, 2013, Alex Deymo wrote:
> Changes from the v4 are:
> * uint32_t --> unsigned int for the "attempt" argument. I think that
> restrict that value to unsigned given that -1 is never used for
> attempt is a good practice.
> * "pincb_iter" --> "btd_adapter_pin_cb_iter". The "pin_cb" instead
> of "pincb" is to match the btd_adapter_pin_cb_t callback type
> already used in the code.
> * Added a bool pincode_requested member to btd_adapter (see patch 4/8)
> to signal if the device requested a pincode during the bonding attempt.
> This is basically to fix the case were we keep retrying the bonding
> and the device keeps sending an authentication error without consuming
> a pin code from the pincode callback list. This ensures that either a
> pincode was consumed from the list before retrying. Together with the
> fact that the pin codes provided by the callback list is a finite list,
> this ensures the retry mechanism will finish.
> 
> Please consider this version for bluez. We are actively testing this
> patchset in our last chromiumos release and I don't have any bug reported
> regarding this feature. Thanks!
> Alex.
> 
> Alex Deymo (8):
>   core: Convert the pincode callback to an interable list.
>   plugins: Extend the pin code callback with the call number
>   core: Add support for retrying a bonding
>   core: retry bonding attempt until the iterator reaches the end.
>   core: Add device_get_class to the public interface.
>   autopair: Add the autopair plugin.
>   core: Expose the last bonding attempt timeout on retry
>   autopair: Try a fixed pincode for keyboards rejecting random codes
> 
>  Makefile.plugins   |   3 +
>  plugins/autopair.c | 165 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  plugins/wiimote.c  |   7 ++-
>  src/adapter.c      | 175 ++++++++++++++++++++++++++++++++++++++++++++++-------
>  src/adapter.h      |  11 +++-
>  src/device.c       | 135 +++++++++++++++++++++++++++++++++++++++++
>  src/device.h       |   7 +++
>  7 files changed, 478 insertions(+), 25 deletions(-)
>  create mode 100644 plugins/autopair.c

All patches in this set have been applied. Thanks!

I did fix one thing in patch 4: for type bool the expected assignments
are true/false and not TRUE/FALSE (which are GLib defines). I also
pushed one small coding style/readability patch on top of this set.

Johan

      parent reply	other threads:[~2013-05-10  7:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  0:37 [PATCH v5 0/8] Autopair Alex Deymo
2013-05-09  0:37 ` [PATCH v5 1/8] core: Convert the pincode callback to an interable list Alex Deymo
2013-05-09  0:37 ` [PATCH v5 2/8] plugins: Extend the pin code callback with the call number Alex Deymo
2013-05-09  0:37 ` [PATCH v5 3/8] core: Add support for retrying a bonding Alex Deymo
2013-05-09  0:37 ` [PATCH v5 4/8] core: retry bonding attempt until the iterator reaches the end Alex Deymo
2013-05-09  0:37 ` [PATCH v5 5/8] core: Add device_get_class to the public interface Alex Deymo
2013-05-09  0:38 ` [PATCH v5 6/8] autopair: Add the autopair plugin Alex Deymo
2013-05-09  0:38 ` [PATCH v5 7/8] core: Expose the last bonding attempt timeout on retry Alex Deymo
2013-05-09  0:38 ` [PATCH v5 8/8] autopair: Try a fixed pincode for keyboards rejecting random codes Alex Deymo
2013-05-10  7:39 ` Johan Hedberg [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=20130510073959.GA32047@x220.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=deymo@chromium.org \
    --cc=keybuk@chromium.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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).