linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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] Write Link Loss Alert level if connected
Date: Tue, 27 Sep 2011 11:25:05 +0300	[thread overview]
Message-ID: <20110927082504.GD3952@dell> (raw)
In-Reply-To: <1312908464-20064-1-git-send-email-claudio.takahasi@openbossa.org>

Hi Claudio,

On Tue, Aug 09, 2011, Claudio Takahasi wrote:
> When SetProperty gets called for LinkLossAlertLevel, the alert level
> can be written in the remote is the link is up.
> ---
>  proximity/monitor.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)

Both patches have been applied. Thanks.

Johan

      parent reply	other threads:[~2011-09-27  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 16:47 [PATCH BlueZ 1/2] Write Link Loss Alert level if connected Claudio Takahasi
2011-08-09 16:47 ` [PATCH BlueZ 2/2] Fix ATT disconnect callback not being called Claudio Takahasi
2011-09-27  8:25 ` 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=20110927082504.GD3952@dell \
    --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;
as well as URLs for NNTP newsgroup(s).