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: Pull request: git://gitorious.org/~lizardo/bluez/lizardo-bluez.git for-upstream
Date: Mon, 4 Oct 2010 17:16:28 +0200	[thread overview]
Message-ID: <20101004151628.GA19781@jh-x301> (raw)
In-Reply-To: <AANLkTimfiie4L6CBm_oTiyFRmB92dt6bugvBREY6vuzN@mail.gmail.com>

Hi,

On Mon, Oct 04, 2010, Anderson Lizardo wrote:
> The following changes since commit bb061d925ad661836d5279b543a07d17683d9b6e:
>   Marcel Holtmann (1):
>         Update list of company identifiers
> 
> are available in the git repository at:
> 
>   git://gitorious.org/~lizardo/bluez/lizardo-bluez.git for-upstream
> 
> Anderson Lizardo (7):
>       Remove unnecessary check for watcher path
>       Rename global "handle" variable to "sdp_handle"
>       Add test/test-attrib for testing Attribute API
>       Add org.bluez.Watcher interface to default policy
>       Fix and refactor characteristic value update code
>       Add Write Characteristic Value support to attribute server
>       Allow errors to propagate from connection callback
> 
> Bruna Moreira (8):
>       Add encoders/decoders for the Write command
>       Implement Write command in GATT API
>       Move connection common code to l2cap_connect()
>       Write new value for characteristic value
>       Use g_slist_foreach() instead of a for loop
>       Make handle parameter mandatory in gatttool
>       Add new option for char value write in gatttool
>       Implement characteristic_write callback in gatttool
> 
>  attrib/att.c        |   45 ++++++++++++++++
>  attrib/att.h        |    4 ++
>  attrib/client.c     |  145 ++++++++++++++++++++++++---------------------------
>  attrib/gatt.c       |   11 ++++
>  attrib/gatt.h       |    3 +
>  attrib/gatttool.c   |  120 ++++++++++++++++++++++++++++++++++++------
>  src/attrib-server.c |   32 ++++++++++--
>  src/bluetooth.conf  |    1 +
>  test/test-attrib    |  120 ++++++++++++++++++++++++++++++++++++++++++
>  9 files changed, 381 insertions(+), 100 deletions(-)
>  create mode 100755 test/test-attrib

Thanks, all patches have been pushed upstream.

Johan

  reply	other threads:[~2010-10-04 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 14:11 Pull request: git://gitorious.org/~lizardo/bluez/lizardo-bluez.git for-upstream Anderson Lizardo
2010-10-04 15:16 ` Johan Hedberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-22 20:37 Anderson Lizardo
2010-09-22 21:04 ` Johan Hedberg
2010-09-22 19:25 Anderson Lizardo
2010-09-22 19:39 ` Johan Hedberg

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=20101004151628.GA19781@jh-x301 \
    --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).