public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bruna Moreira <bruna.moreira@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 BlueZ 3/4] device: Appearance characteristic from GAP service
Date: Fri, 30 Mar 2012 14:35:56 +0300	[thread overview]
Message-ID: <20120330113556.GA13864@x220> (raw)
In-Reply-To: <1333031882-15644-1-git-send-email-bruna.moreira@openbossa.org>

Hi Bruna,

On Thu, Mar 29, 2012, Bruna Moreira wrote:
> After searching for primary services, the appearance characteristic is
> read from GAP service and saved in "appearance" file. Running
> GetProperty in device interface, will show the respective icon based in
> "appearance" value.
> ---
>  src/device.c |   70 ++++++++++++++++++++++++++++++++++++++++++++++++++++-----
>  1 files changed, 63 insertions(+), 7 deletions(-)

All four patches in this set have been applied. Thanks.

Johan

      reply	other threads:[~2012-03-30 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 13:29 [PATCH BlueZ 0/4] GAP device Appearance support Bruna Moreira
2012-03-27 13:29 ` [PATCH BlueZ 1/4] dbus-common: Map GAP Appearance characteristic to icon Bruna Moreira
2012-03-27 13:29 ` [PATCH BlueZ 2/4] storage: Add storage to GAP characteristic Bruna Moreira
2012-03-27 13:29 ` [PATCH BlueZ 3/4] device: Appearance characteristic from GAP service Bruna Moreira
2012-03-28  9:58   ` Johan Hedberg
2012-03-29 14:22     ` Bruna Moreira
2012-03-27 13:29 ` [PATCH BlueZ 4/4] eir: Read GAP appearance from advertising data Bruna Moreira
2012-03-27 15:11   ` Johan Hedberg
2012-03-27 18:06   ` [PATCH v2 BlueZ] " Bruna Moreira
2012-03-29 14:38 ` [PATCH v2 BlueZ 3/4] device: Appearance characteristic from GAP service Bruna Moreira
2012-03-30 11:35   ` 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=20120330113556.GA13864@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=bruna.moreira@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