linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kan-Ru Chen <kanru@kanru.info>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: nsathish41@gmail.com, linux-bluetooth@vger.kernel.org,
	chethan.tumkur.narayan@intel.com, ravishankar.srivatsa@intel.com,
	kiran.k@intel.com, sathish.narasimman@intel.com
Subject: Re: [PATCH] Bluetooth: Fix: LL PRivacy BLE device fails to connect
Date: Sun, 27 Dec 2020 02:02:34 +0900	[thread overview]
Message-ID: <87mty0bivp.fsf@shinagawa> (raw)
In-Reply-To: <4DB44FB6-A6F3-4FBE-A16D-EE3FCB1A6F65@holtmann.org> (message from Marcel Holtmann on Mon, 9 Nov 2020 13:41:10 +0100)

Hi,

Marcel Holtmann <marcel@holtmann.org> writes:

> 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.

Can we also apply this patch to the 5.10 stable tree?

Thanks,
Kanru

  reply	other threads:[~2020-12-26 17:04 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
2020-12-26 17:02   ` Kan-Ru Chen [this message]
  -- 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=87mty0bivp.fsf@shinagawa \
    --to=kanru@kanru.info \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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).