From: Johan Hedberg <johan.hedberg@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix conditions for HCI_Delete_Stored_Link_Key
Date: Thu, 13 Jun 2013 12:07:03 +0300 [thread overview]
Message-ID: <20130613090703.GA16626@x220> (raw)
In-Reply-To: <20130613084521.GA3651@amd.pavel.ucw.cz>
Hi Pavel,
On Thu, Jun 13, 2013, Pavel Machek wrote:
> > Therefore, it makes sense to move sending of HCI_Delete_Stored_Link_Key
> > to after receiving the supported commands response and to only send it
> > if its respective bit in the mask is set. The downside of this is that
> > we no longer send the HCI_Delete_Stored_Link_Key command for Bluetooth
> > 1.1 controllers since HCI_Read_Local_Supported_Command was introduced in
> > version 1.2, but this is an acceptable penalty as the command in
> > question shouldn't affect critical behavior.
> >
> > Reported-by: Pavel Machek <pavel@ucw.cz>
> > Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
>
> Tested-by: Pavel Machek <pavel@ucw.cz>
Thanks!
> (Addiditonaly, if you are right and this was in 3.9 already, we
> probably want to cc: stable@kernel.org).
Even though the command itself was in 3.9 it wasn't using the request
framework that was introduced in 3.10 (which for now is depending on all
commands succeeding) so I think you're right after all that it's an
regression since 3.9. Also, because this patch uses the API of the
request framework (hci_req_add) it will not be trivially backportable to
older kernels, so I'd just forget about cc:stable.
Johan
next prev parent reply other threads:[~2013-06-13 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 8:01 [PATCH] Bluetooth: Fix conditions for HCI_Delete_Stored_Link_Key Johan Hedberg
2013-06-13 8:45 ` Pavel Machek
2013-06-13 9:07 ` Johan Hedberg [this message]
2013-06-13 9:59 ` Gustavo Padovan
2013-06-13 10:34 ` Marcel Holtmann
2013-06-13 10:42 ` Gustavo Padovan
2013-06-13 10:48 ` Marcel Holtmann
2013-06-13 11:25 ` Gustavo Padovan
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=20130613090703.GA16626@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.