From 33c46f56588911f89b64d03698462987ac8caf4f Mon Sep 17 00:00:00 2001
From: Donatien Garnier <donatien.garnier@arm.com>
Date: Sun, 13 May 2018 17:49:00 +0100
Subject: [PATCH] Remove LL resolving 'shorcut' when adding a device to
 resolving list - this should be controlled by the GAP layer

---
 .../TARGET_CORDIO/source/CordioPalSecurityManager.cpp        | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/features/FEATURE_BLE/targets/TARGET_CORDIO/source/CordioPalSecurityManager.cpp b/features/FEATURE_BLE/targets/TARGET_CORDIO/source/CordioPalSecurityManager.cpp
index 2adb350699..46df438db8 100644
--- a/features/FEATURE_BLE/targets/TARGET_CORDIO/source/CordioPalSecurityManager.cpp
+++ b/features/FEATURE_BLE/targets/TARGET_CORDIO/source/CordioPalSecurityManager.cpp
@@ -777,11 +777,8 @@ struct CordioSecurityManager::PrivacyAddDevToResListControlBlock : CordioSecurit
     virtual ~PrivacyAddDevToResListControlBlock() {}
 
     virtual void execute() {
-        // Check whether we need to enable resolution in LL
-        bool enable_ll_resolving = !DmLlPrivEnabled();
-
         // Execute command
-        DmPrivAddDevToResList(_peer_identity_address_type.value(), _peer_identity_address.data(), _peer_irk.data(), DmSecGetLocalIrk(), enable_ll_resolving, 0);
+        DmPrivAddDevToResList(_peer_identity_address_type.value(), _peer_identity_address.data(), _peer_irk.data(), DmSecGetLocalIrk(), false, 0);
     }
 
 private: