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;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: [PATCH v2 0/7] LL Privacy support
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <20200603171713.9882-1-sathish.narasimman@intel.com>
Date:   Fri, 19 Jun 2020 09:58:23 +0200
Cc:     Bluetooth Kernel Mailing List <linux-bluetooth@vger.kernel.org>,
        Sathish Narasimman <sathish.narasimman@intel.com>
Content-Transfer-Encoding: 8BIT
Message-Id: <ACE20ACA-6CE3-4348-88E2-D38DF6680C7F@holtmann.org>
References: <20200603171713.9882-1-sathish.narasimman@intel.com>
To:     Sathish Narasimman <nsathish41@gmail.com>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Sathish,

> Based on the input the patches modified and verifed accordingly.
> 
> Marcel Holtmann (3):
>  Bluetooth: Translate additional address type correctly
>  Bluetooth: Configure controller address resolution if available
>  Bluetooth: Update resolving list when updating whitelist
> 
> Sathish Narasimman (4):
>  Bluetooth: Translate additional address type during le_conn
>  Bluetooth: Let controller creates RPA during le create conn
>  Bluetooth: Enable/Disable address resolution during le create conn
>  Bluetooth: Enable RPA Timeout
> 
> include/net/bluetooth/hci.h      |   8 ++-
> include/net/bluetooth/hci_core.h |   3 +
> net/bluetooth/hci_conn.c         |   6 +-
> net/bluetooth/hci_core.c         |  17 +++++
> net/bluetooth/hci_event.c        |  20 ++++++
> net/bluetooth/hci_request.c      | 119 ++++++++++++++++++++++++++-----
> net/bluetooth/hci_request.h      |   3 +-
> net/bluetooth/mgmt.c             |   2 +-
> 8 files changed, 157 insertions(+), 21 deletions(-)

can you please rebase this against the latest bluetooth-next tree. With the introduction of the advertising monitor, we now have a few conflicts that you need to resolve.

Also as discussed, we wanted to hide this initially after an experimental feature flag so it would need to be enabled first. And I think once enabled, we need to take the support of “advertising” aka peripheral away from the controller until we can fully ensure it works for scanning and advertising at the same time.

Regards

Marcel