Deprecate meta-xilinx - Remove the LmP direct support #1553
+0
−5,479
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The plan is to include it as a partner layer, this way we can better handle versioning. Signed-off-by: Daiane Angolini <[email protected]>
Signed-off-by: Daiane Angolini <[email protected]>
Signed-off-by: Daiane Angolini <[email protected]>
Signed-off-by: Daiane Angolini <[email protected]>
Signed-off-by: Daiane Angolini <[email protected]>
Signed-off-by: Daiane Angolini <[email protected]>
Signed-off-by: Daiane Angolini <[email protected]>
angolini
requested review from
quaresmajose,
ricardosalveti,
mike-scott and
a team
and removed request for
quaresmajose
|
Should we drop in a big commit and move the current logic to a meta-partner layer? I know we want to remove it from this layer, but we will have to add it all over again once we bring the latest bsp in a partner layer. |
|
I think we can keep these removal commits and mimic them when we add these back to a partner layer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The plan is to have the support added as an partner layer, this way we can easier handle versioning.
This patch was created basically searching (find and grep) for the following keywords:
I personally prefer one huge commit, please let me know what would be the best way to cluster the changes.
I tested by trying to build the removed images, but this is not good enough. So any idea on how to better test it, please let me know