linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] Add missing "Legacy" property for LE devices
Date: Thu, 12 Jan 2012 21:41:55 +0200	[thread overview]
Message-ID: <20120112194155.GC7453@fusion.localdomain> (raw)
In-Reply-To: <1326394781-465-1-git-send-email-anderson.lizardo@openbossa.org>

Hi Lizardo,

On Thu, Jan 12, 2012, Anderson Lizardo wrote:
> Some UIs may assume that a device lacking the Legacy property is
> pre 2.1. To be more consistent with BR/EDR devices, always set Legacy
> property explicitly to False. This makes these UIs not ask for a PIN
> code when doing Just Works pairing for LE devices.
> ---
>  src/adapter.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)

Applied. Thanks.

Johan

      reply	other threads:[~2012-01-12 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 18:59 [PATCH BlueZ] Add missing "Legacy" property for LE devices Anderson Lizardo
2012-01-12 19:41 ` 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=20120112194155.GC7453@fusion.localdomain \
    --to=johan.hedberg@gmail.com \
    --cc=anderson.lizardo@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).