Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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
In-Reply-To: <4DB44FB6-A6F3-4FBE-A16D-EE3FCB1A6F65@holtmann.org> (message
 from Marcel Holtmann on Mon, 9 Nov 2020 13:41:10 +0100)
Date:   Sun, 27 Dec 2020 02:02:34 +0900
Message-ID: <87mty0bivp.fsf@shinagawa>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

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