From: Johan Hedberg <johan.hedberg@gmail.com>
To: Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] Fix wrong write GATT-subprocedure for Link Loss
Date: Wed, 5 Oct 2011 11:18:59 +0300 [thread overview]
Message-ID: <20111005081859.GA11882@fusion.localdomain> (raw)
In-Reply-To: <1317748963-13176-1-git-send-email-claudio.takahasi@openbossa.org>
Hi Claudio,
On Tue, Oct 04, 2011, Claudio Takahasi wrote:
> According to Link Loss Service specification, Write Characteristic
> Value sub-procedure should be used to change the Alert Level.
> ---
> proximity/monitor.c | 25 +++++++++++++++++++++----
> 1 files changed, 21 insertions(+), 4 deletions(-)
Both patches applied. Thanks.
Johan
prev parent reply other threads:[~2011-10-05 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 17:22 [PATCH BlueZ 1/2] Fix wrong write GATT-subprocedure for Link Loss Claudio Takahasi
2011-10-04 17:22 ` [PATCH BlueZ 2/2] Emit LinkLossAlertLevel after writing the alert Claudio Takahasi
2011-10-05 8:18 ` Johan Hedberg [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=20111005081859.GA11882@fusion.localdomain \
--to=johan.hedberg@gmail.com \
--cc=claudio.takahasi@openbossa.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