From: Arman Uguray <armansito@chromium.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Gu, Chao Jie" <chao.jie.gu@intel.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC v1 1/1] doc/gatt-api: New API properties and methods for the GATT D-Bus API.
Date: Mon, 11 Aug 2014 11:46:00 -0700 [thread overview]
Message-ID: <CAHrH25SgBJSF=X+-qhFwSWjjqWHZuthHp4bFL2OXcUdTF_WWkg@mail.gmail.com> (raw)
In-Reply-To: <B24F6699-B579-455E-8D83-9922ED923CAA@holtmann.org>
Hi Marcel,
> I have no major objections to the API, but just an API description is not enough. What is important to also deliver an implementation of this API.
>
The implementation will come in the next few months as the shared
stack takes shape. The thing is, the existing proposal is not
accompanied by an implementation (it's not even included in the
release bundles) either and it looks like there are several parties
that are implementing their own version of the API based on the
unimplemented proposal. I think it makes sense to update it with the
changes that we discussed so that people can plan their code for
future compatibility.
Either that or remove doc/gatt-api.txt entirely for the time being.
-Arman
next prev parent reply other threads:[~2014-08-11 18:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 23:40 [RFC v1 0/1] doc/gatt-api: New API properties and methods for the GATT D-Bus API Arman Uguray
2014-07-21 23:40 ` [RFC v1 1/1] " Arman Uguray
2014-07-22 8:38 ` guchaojie
2014-07-28 9:17 ` Gu, Chao Jie
2014-07-28 20:52 ` Arman Uguray
2014-07-28 22:34 ` Marcel Holtmann
2014-07-28 23:31 ` Arman Uguray
2014-07-28 23:51 ` Marcel Holtmann
2014-07-29 6:03 ` Gu, Chao Jie
2014-07-29 19:07 ` Arman Uguray
2014-07-30 16:46 ` Marcel Holtmann
2014-08-01 3:11 ` Arman Uguray
2014-08-11 9:56 ` Gu, Chao Jie
2014-08-11 17:49 ` Marcel Holtmann
2014-08-11 18:46 ` Arman Uguray [this message]
2014-08-11 19:03 ` Marcel Holtmann
2014-08-11 20:38 ` Arman Uguray
2014-07-22 8:55 ` [RFC v1 0/1] " Johan Hedberg
2014-07-22 20:40 ` Arman Uguray
2014-07-23 5:24 ` Marcin Kraglak
2014-07-23 16:20 ` Arman Uguray
2014-07-23 13:22 ` Gu, Chao Jie
2014-07-23 16:18 ` Arman Uguray
2014-07-23 16:32 ` Marcel Holtmann
2014-07-23 20:39 ` Arman Uguray
2014-07-24 4:11 ` Gu, Chao Jie
2014-07-24 7:58 ` Luiz Augusto von Dentz
2014-07-24 8:01 ` Luiz Augusto von Dentz
2014-07-25 18:50 ` Arman Uguray
2014-07-25 19:17 ` Luiz Augusto von Dentz
2014-07-25 19:28 ` Marcel Holtmann
2014-07-25 21:06 ` Arman Uguray
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='CAHrH25SgBJSF=X+-qhFwSWjjqWHZuthHp4bFL2OXcUdTF_WWkg@mail.gmail.com' \
--to=armansito@chromium.org \
--cc=chao.jie.gu@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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.