Merge pull request #13357 from rajkan01/emac_dir_restructure

Move emac-drivers from features into connectivity directory

.astyleignore

@@ -2,6 +2,7 @@
 ^cmsis
 ^connectivity/libraries/mbed-coap
 ^connectivity/libraries/ppp
+^connectivity/drivers/emac
 ^features/cryptocell
 ^features/FEATURE_BLE
 ^features/FEATURE_EXPERIMENTAL_API/FEATURE_PSA/TARGET_MBED_PSA_SRV
@@ -12,7 +13,6 @@
 ^features/mbedtls
 ^features/nanostack/sal-stack-nanostack/source/Service_Libs/mdns/fnet
 ^features/nanostack/targets
-^features/netsocket/emac-drivers
 ^storage/filesystem/fat/ChaN
 ^storage/filesystem/littlefs/littlefs/
 ^storage/filesystem/littlefsv2/littlefs/

LICENSE.md

@@ -4,7 +4,8 @@ as can be found in: LICENSE-apache-2.0.txt
 Folders containing files under different permissive license than Apache 2.0 are listed below. Each folder should contain its own README file with license specified for its files. The original license text is included in those source files.
 
 - [cmsis](./cmsis) - MIT, BSD-3-Clause
-- [components/802.15.4_RF/mcr20a-rf-driver](./components/802.15.4_RF/mcr20a-rf-driver) - BSD-3-Clause
+- [connectivity/drivers/802.15.4_RF/mcr20a-rf-driver](./connectivity/drivers/802.15.4_RF/mcr20a-rf-driver) - BSD-3-Clause
+- [connectivity/drivers/emac](./connectivity/drivers/emac) - BSD-style
 - [features/cryptocell/FEATURE_CRYPTOCELL310](./features/cryptocell/FEATURE_CRYPTOCELL310) - ARM Object Code and Header Files License
 - [features/FEATURE_BOOTLOADER](./features/FEATURE_BOOTLOADER) - PBL
 - [features/FEATURE_BLE/targets](./features/FEATURE_BLE/targets) - BSD-style, PBL, MIT-style
@@ -14,7 +15,6 @@ Folders containing files under different permissive license than Apache 2.0 are
 - [features/lorawan](./features/lorawan) - Revised BSD
 - [features/lwipstack](./features/lwipstack) - BSD-style, MIT-style
 - [features/nanostack/sal-stack-nanostack](./features/nanostack/sal-stack-nanostack) - BSD-3-Clause
-- [features/netsocket/emac-drivers](./features/netsocket/emac-drivers) - BSD-style
 - [features/frameworks/unity/unity](./features/frameworks/unity/unity) - MIT
 - [features/unsupported](./features/unsupported) - MIT-style, BSD-style
 - [storage/blockdevice](./storage/blockdevice) - Apache 2.0, MIT

connectivity/drivers/emac/README.md

@@ -32,7 +32,7 @@ to control your device. This must be derived from class `EMAC`.
 This API is used by a network stack (or test framework) to control your driver.
 
 The EMAC-derived driver would normally be installed in
-features/netsocket/emac-drivers, often in a `TARGET_XXX` directory.
+connectivity/drivers/emac, often in a `TARGET_XXX` directory.
 
 Class EMAC is entirely abstract - you need to implement about a dozen calls
 to activate the driver, send and receive packets, and perform other control