All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arman Uguray <armansito@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Arman Uguray <armansito@chromium.org>
Subject: [PATCH BlueZ v2 0/7] shared/gatt-client: Handle notifications.
Date: Wed, 10 Sep 2014 09:36:20 -0700	[thread overview]
Message-ID: <1410366987-8128-1-git-send-email-armansito@chromium.org> (raw)

*v2:
   - Renames:
     - not_id -> notify_id
     - not_ref_count -> notify_count
     - ind_id -> indic_id -> indication_id -> ind_id

   - Fixed typo in tools/btgatt-client.

*v1: Handled style comments:
   - Renamed some variables to make them more meaningful.
   - Moved functions around to avoid forward declarations as much as possible.
   - Added an internal bt_gatt_descriptor_t pointer to struct chrc_data while
     keeping the external const pointer in bt_gatt_descriptor_t, both of which
     point to the same array of descriptors.

Arman Uguray (7):
  shared/gatt-client: Introduce struct bt_gatt_characteristic_iter.
  shared/gatt-client: Implement bt_gatt_client_register_notify.
  shared/gatt-client: Implement bt_gatt_client_unregister_notify.
  shared/gatt-client: Handle incoming not/ind PDUs.
  tools/btgatt-client: Add the "register-notify" command.
  tools/btgatt-client: Add "unregister-notify" command.
  TODO: Reference counted notify functions implemented

 TODO                      |  10 -
 src/shared/gatt-client.c  | 564 +++++++++++++++++++++++++++++++++++++++++-----
 src/shared/gatt-client.h  |  57 ++++-
 src/shared/gatt-helpers.c |  67 ------
 src/shared/gatt-helpers.h |   9 -
 tools/btgatt-client.c     | 139 ++++++++++--
 6 files changed, 684 insertions(+), 162 deletions(-)

-- 
2.1.0.rc2.206.gedb03e5


             reply	other threads:[~2014-09-10 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 16:36 Arman Uguray [this message]
2014-09-10 16:36 ` [PATCH BlueZ v2 1/7] shared/gatt-client: Introduce struct bt_gatt_characteristic_iter Arman Uguray
2014-09-10 16:36 ` [PATCH BlueZ v2 2/7] shared/gatt-client: Implement bt_gatt_client_register_notify Arman Uguray
2014-09-10 16:36 ` [PATCH BlueZ v2 3/7] shared/gatt-client: Implement bt_gatt_client_unregister_notify Arman Uguray
2014-09-10 16:36 ` [PATCH BlueZ v2 4/7] shared/gatt-client: Handle incoming not/ind PDUs Arman Uguray
2014-09-10 16:36 ` [PATCH BlueZ v2 5/7] tools/btgatt-client: Add the "register-notify" command Arman Uguray
2014-09-10 16:36 ` [PATCH BlueZ v2 6/7] tools/btgatt-client: Add "unregister-notify" command Arman Uguray
2014-09-10 16:36 ` [PATCH BlueZ v2 7/7] TODO: Reference counted notify functions implemented Arman Uguray
2014-09-11  0:58 ` [PATCH BlueZ v2 0/7] shared/gatt-client: Handle notifications Marcel Holtmann

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=1410366987-8128-1-git-send-email-armansito@chromium.org \
    --to=armansito@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.