From: Marcel Holtmann <marcel@holtmann.org>
To: Sathish Narasimman <nsathish41@gmail.com>
Cc: "open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
Chethan T N <chethan.tumkur.narayan@intel.com>,
"Srivatsa, Ravishankar" <ravishankar.srivatsa@intel.com>,
kiran.k@intel.com,
Sathish Narasimman <sathish.narasimman@intel.com>
Subject: Re: [PATCH] Bluetooth: Fix: LL PRivacy BLE device fails to connect
Date: Mon, 9 Nov 2020 13:41:10 +0100 [thread overview]
Message-ID: <4DB44FB6-A6F3-4FBE-A16D-EE3FCB1A6F65@holtmann.org> (raw)
In-Reply-To: <20201029074821.29950-1-sathish.narasimman@intel.com>
Hi Sathish,
> When adding device to white list the device is added to resolving list
> also. It has to be added only when HCI_ENABLE_LL_PRIVACY flag is set.
> HCI_ENABLE_LL_PRIVACY flag has to be tested before adding/deleting devices
> to resolving list. use_ll_privacy macro is used only to check if controller
> supports LL_Privacy.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=209745
>
> Fixes: 0eee35bdfa3b ("Bluetooth: Update resolving list when updating whitelist")
>
> Signed-off-by: Sathish Narasimman <sathish.narasimman@intel.com>
> ---
> net/bluetooth/hci_request.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
next prev parent reply other threads:[~2020-11-09 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 7:48 [PATCH] Bluetooth: Fix: LL PRivacy BLE device fails to connect Sathish Narasimman
2020-11-03 2:05 ` Narasimman, Sathish
2020-11-09 12:41 ` Marcel Holtmann [this message]
2020-12-26 17:02 ` Kan-Ru Chen
-- strict thread matches above, loose matches on Subject: below --
2020-10-22 8:23 Sathish Narasimman
2020-10-28 5:30 ` Sathish Narasimman
2020-10-29 0:22 ` Luiz Augusto von Dentz
2020-10-29 7:27 ` Narasimman, Sathish
2020-10-29 0:20 ` Luiz Augusto von Dentz
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=4DB44FB6-A6F3-4FBE-A16D-EE3FCB1A6F65@holtmann.org \
--to=marcel@holtmann.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=nsathish41@gmail.com \
--cc=ravishankar.srivatsa@intel.com \
--cc=sathish.narasimman@intel.com \
/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).