From: Marcel Holtmann <marcel@holtmann.org>
To: johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: Don't send unnecessary write_le_enable command
Date: Mon, 27 Feb 2012 15:43:05 -0800 [thread overview]
Message-ID: <1330386185.3392.72.camel@aeonflux> (raw)
In-Reply-To: <1330386094-19501-1-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
> If the local host features indicate that LE is already in the state that
> is desired there's no point in sending the HCI command to try to change
> the setting.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> net/bluetooth/mgmt.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2012-02-27 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 23:41 [PATCH 1/2] Bluetooth: Don't send unnecessary write_le_enable command johan.hedberg
2012-02-27 23:41 ` [PATCH 2/2] Bluetooth: Remove redundant read_host_features commands johan.hedberg
2012-02-28 8:01 ` Andrei Emeltchenko
2012-02-28 8:53 ` Johan Hedberg
2012-02-27 23:43 ` Marcel Holtmann [this message]
2012-02-28 17:31 ` [PATCH 1/2] Bluetooth: Don't send unnecessary write_le_enable command Andre Guedes
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=1330386185.3392.72.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=johan.hedberg@gmail.com \
--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).