Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 0/5]android/gatt: GATT Client write types support
Date: Wed, 23 Apr 2014 15:19:18 +0200	[thread overview]
Message-ID: <1947887.Wb3RGBOdof@leonov> (raw)
In-Reply-To: <1397735868-19092-1-git-send-email-lukasz.rymanowski@tieto.com>

Hi Łukasz,

On Thursday 17 of April 2014 13:57:43 Lukasz Rymanowski wrote:
> This patch set adds support for different write types.
> For this I had to expose some additional API from attrib.
> 
> Only signed write left to implement.
> 
> v2:
> * Rebase
> * Remove double empty line from gatt.h as Szymon pointed out
> 
> Lukasz Rymanowski (5):
>   attrib: Add API for reliable write
>   attrib: Expose write execute
>   android/gatt: Add support for reliable write
>   android/gatt: Add support for write execute
>   android/gatt: Add support for write without response
> 
>  android/gatt.c | 113
> ++++++++++++++++++++++++++++++++++++++++++++++++--------- attrib/gatt.c  | 
> 24 ++++++++++++
>  attrib/gatt.h  |   8 ++++
>  3 files changed, 128 insertions(+), 17 deletions(-)

All patches applied, thanks.

-- 
BR
Szymon Janc

      parent reply	other threads:[~2014-04-23 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 11:57 [PATCH v2 0/5]android/gatt: GATT Client write types support Lukasz Rymanowski
2014-04-17 11:57 ` [PATCH v2 1/5] attrib: Add API for reliable write Lukasz Rymanowski
2014-04-17 11:57 ` [PATCH v2 2/5] attrib: Expose write execute Lukasz Rymanowski
2014-04-17 11:57 ` [PATCH v2 3/5] android/gatt: Add support for reliable write Lukasz Rymanowski
2014-04-17 11:57 ` [PATCH v2 4/5] android/gatt: Add support for write execute Lukasz Rymanowski
2014-04-17 11:57 ` [PATCH v2 5/5] android/gatt: Add support for write without response Lukasz Rymanowski
2014-04-23 13:19 ` Szymon Janc [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=1947887.Wb3RGBOdof@leonov \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@tieto.com \
    /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