Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Pull request: git://git.infradead.org/users/cktakahasi/bluez.git for-upstream
Date: Mon, 4 Oct 2010 22:43:20 +0200	[thread overview]
Message-ID: <20101004204320.GA11846@jh-x301> (raw)
In-Reply-To: <AANLkTinF1OWKMzuArUS6ptWiDTtvQuXxxW9B5ks3tebW@mail.gmail.com>

Hi Claudio,

On Mon, Oct 04, 2010, Claudio Takahasi wrote:
> The following changes since commit 19c8e310329bb6b369f11501afec9ff4223c2971:
> 
>   Allow errors to propagate from connection callback (2010-10-04 17:06:49 +0200)
> 
> are available in the git repository at:
>   git://git.infradead.org/users/cktakahasi/bluez.git for-upstream
> 
> Claudio Takahasi (23):
>       Add LE start and stop scanning
>       Remove RSSI field from the advertising report event
>       Decoding the RSSI parameter from the advertising report event
>       Send Discovering property "FALSE" when the interleave finishes
>       Add length argument on hciops start discovery function
>       Stop inquiry using the length parameter
>       Fix remote name resolution for interleave discovery
>       Add Write LE host supported function
>       Set the LE host supported and disable simultaneous LE and BR/EDR flags
>       Add extended feature mask constants definition
>       Read the local extended features
>       Stop LE scanning when discovery is suspended
>       Rename hciops {start, stop}_discovery to {start, stop}_inquiry
>       Don't enter on interleave mode if there isn't active sessions
>       Code cleanup: improving inquiry logic
>       Clear the remote device found list in the state transition
>       Fix periodic inquiry signals
>       Fixing DeviceDisappeared signal
>       Postpone discovery if still resolving names
>       Add adapter discovery type function
>       Do not send another Discovering TRUE signal if still resolving names
>       Forcing periodic inquiry exit
>       Fix interleave scanning
> 
> Vinicius Costa Gomes (1):
>       Add BR/EDR LE interleaved discovery
> 
>  lib/hci.c        |   29 +++++
>  lib/hci.h        |   17 +++-
>  lib/hci_lib.h    |    1 +
>  plugins/hciops.c |   69 +++++++++++-
>  src/adapter.c    |  301 +++++++++++++++++++++++++++++++++++++-----------------
>  src/adapter.h    |   38 ++++---
>  src/dbus-hci.c   |   45 +++++++--
>  src/dbus-hci.h   |    1 +
>  src/security.c   |  131 ++++++++++++++----------
>  9 files changed, 449 insertions(+), 183 deletions(-)

Thanks. Pushed upstream.

Johan

      reply	other threads:[~2010-10-04 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 16:19 Pull request: git://git.infradead.org/users/cktakahasi/bluez.git for-upstream Claudio Takahasi
2010-09-23 17:55 ` Luiz Augusto von Dentz
2010-09-23 18:07   ` Claudio Takahasi
2010-09-29 13:45 ` Johan Hedberg
2010-09-29 14:05   ` Claudio Takahasi
2010-09-30  7:39     ` Johan Hedberg
2010-09-30 14:28       ` Claudio Takahasi
2010-09-30 21:51         ` Claudio Takahasi
2010-10-04 17:27           ` Claudio Takahasi
2010-10-04 20:43             ` 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=20101004204320.GA11846@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=claudio.takahasi@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