Linux bluetooth development
 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 0/8] shared/gatt: Use gatt-db for client role.
Date: Fri, 28 Nov 2014 09:49:14 -0800	[thread overview]
Message-ID: <1417196962-3876-1-git-send-email-armansito@chromium.org> (raw)

This patch set integrates shared/gatt-db into shared/gatt-client:
  1. shared/gatt-client's internal service_list structure has been
     removed entirely in favor of gatt-db.
  2. The high level structures defined in gatt-client.h
     (bt_gatt_service_t, bt_gatt_characteristic_t, bt_gatt_descriptor_t)
     and the corresponding iterator structures and functions have been
     removed.
  3. Code using the iterators (unit/test-gatt, tools/btgatt*) now access
     the client cache via gatt-client's gatt-db.
  4. Small bug fixes in gatt-db.

Arman Uguray (8):
  shared/gatt-db: Fix bug in maximum handle check.
  shared/gatt-db: Add helper to get service handles.
  shared/gatt-client: Store services in gatt_db.
  shared/gatt-client: Use gatt_db in bt_gatt_register_notify
  tools/btgatt-server: Add the "services" command
  tools/btgatt-client: Use gatt-db instead of iterators
  unit/test-gatt: Use gatt-db for CLIENT tests
  shared/gatt-client: Remove GATT structs and iterators

 src/shared/gatt-client.c | 1189 +++++++++++++++++++++-------------------------
 src/shared/gatt-client.h |   73 +--
 src/shared/gatt-db.c     |   41 +-
 tools/btgatt-client.c    |  175 +++----
 tools/btgatt-server.c    |   90 ++++
 unit/test-gatt.c         |  241 +++++++---
 6 files changed, 911 insertions(+), 898 deletions(-)

-- 
2.2.0.rc0.207.ga3a616c


             reply	other threads:[~2014-11-28 17:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 17:49 Arman Uguray [this message]
2014-11-28 17:49 ` [PATCH BlueZ 1/8] shared/gatt-db: Fix bug in maximum handle check Arman Uguray
2014-11-28 17:49 ` [PATCH BlueZ 2/8] shared/gatt-db: Add helper to get service handles Arman Uguray
2014-11-28 17:49 ` [PATCH BlueZ 3/8] shared/gatt-client: Store services in gatt_db Arman Uguray
2014-12-01  9:45   ` Luiz Augusto von Dentz
2014-12-01 14:50     ` Arman Uguray
2014-12-01 16:02       ` Luiz Augusto von Dentz
2014-12-01 16:37         ` Arman Uguray
2014-12-01 17:19           ` Marcel Holtmann
2014-12-01 17:57             ` Arman Uguray
2014-12-02 10:46               ` Luiz Augusto von Dentz
2014-12-02 15:12                 ` Luiz Augusto von Dentz
2014-12-02 19:35                   ` Arman Uguray
2014-12-03  0:15                     ` Arman Uguray
2014-11-28 17:49 ` [PATCH BlueZ 4/8] shared/gatt-client: Use gatt_db in bt_gatt_register_notify Arman Uguray
2014-11-28 17:49 ` [PATCH BlueZ 5/8] tools/btgatt-server: Add the "services" command Arman Uguray
2014-11-28 17:49 ` [PATCH BlueZ 6/8] tools/btgatt-client: Use gatt-db instead of iterators Arman Uguray
2014-11-28 17:49 ` [PATCH BlueZ 7/8] unit/test-gatt: Use gatt-db for CLIENT tests Arman Uguray
2014-11-28 17:49 ` [PATCH BlueZ 8/8] shared/gatt-client: Remove GATT structs and iterators Arman Uguray
2014-12-01  9:49 ` [PATCH BlueZ 0/8] shared/gatt: Use gatt-db for client role Luiz Augusto von Dentz

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=1417196962-3876-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox