Fix duplication of KW41Z Nanostack driver #13230
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
In #13119 we moved Nanostack target drivers into
nanostack-interface/targets
, to fix issues with bare-metal (i.e. nombed_lib.json
to guard unused libraries). But at roughly the same time, #13115 (renameTARGET_NXP
toTARGET_Freescale
) was made in the old path. Now we end up with identical KW41Z drivers in two different places.This PR resolves the issue:
nanostack-interface/targets
as per Move target implementations of NanostackRfPhy into nanostack-interface #13119TARGET_Freescale
instead ofTARGET_NXP
as per MIMXRT1050_EVK: Add USB support #13115Impact of changes
Migration actions required
Documentation
None.
Pull request type
Test results
Manual testing: both mbed-os-example-blinky and mbed-os-example-blinky-baremetal compile for KW41Z.
Reviewers
@MarceloSalazar @evedon