merge: Currency merge with upstream hardknott branch #6
Conversation
This file contains hidden or 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
Signed-off-by: Philip Balister <[email protected]>
* Drop upstreamed patches. Signed-off-by: Philip Balister <[email protected]>
…ardknott Signed-off-by: Gratian Crisan <[email protected]>
Author
|
Attn: @amstewart @shruthi-ravi Btw. I would have set reviewers/assignees directly but I don't seem to have the required permissions for this repo. |
shruthi-ravi
approved these changes
Apr 25, 2022
amstewart
approved these changes
Apr 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This is the 2022Q2.1 currency merge with upstream hardknott branch.
There were no merge conflicts and no additional NI-specific patches are required.
Testing
Upstream ref: hardknott
AzDO 1848521
Procedural note
Maintainers please wait to pull this until PRs to other hardknott layers are ready.
Currently tracking one upstream issue in meta-openembedded, PR 569
@ni/rtos