Return-Path: <cyrus@holtmann.org>
MIME-Version: 1.0
In-Reply-To: <CABD6X-JthdBhBqfdstMogPsbaHh=Z-KpTJbYut2iDjW-7gsoSw@mail.gmail.com>
References: <1405986034-29122-1-git-send-email-armansito@chromium.org>
	<20140722085507.GA29664@t440s.lan>
	<CAHrH25SR83cXq-xGQz4x7axjcW=CUL_VCcAfhny_RyZ+t0oZ-g@mail.gmail.com>
	<CABD6X-JthdBhBqfdstMogPsbaHh=Z-KpTJbYut2iDjW-7gsoSw@mail.gmail.com>
Date: Wed, 23 Jul 2014 09:20:11 -0700
Message-ID: <CAHrH25R4zdn2iwHCRg1=hbtwjaG__GaQ6T-6JPjNH+b93KzHPA@mail.gmail.com>
Subject: Re: [RFC v1 0/1] doc/gatt-api: New API properties and methods for the
 GATT D-Bus API.
From: Arman Uguray <armansito@google.com>
To: Marcin Kraglak <marcin.kraglak@tieto.com>
Cc: Arman Uguray <armansito@chromium.org>,
	BlueZ development <linux-bluetooth@vger.kernel.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	"Gu, Chao Jie" <chao.jie.gu@intel.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Hi Marcin,

> We could also add Invalid Value Length error.

Good point, I will add that to the list of errors for WriteValue.

Cheers,
Arman