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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manifest: update cmsis-nn to v6.0.0 & tflite-micro #73995
manifest: update cmsis-nn to v6.0.0 & tflite-micro #73995
Changes from all commits
ae6c525
16446ca
f06b9b0
5c87127
99262be
692b5a2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on what we do for other modules (e.g. TF-M), it would make more sense to merge the CMSIS-NN v6.0.0 tag into the existing
zephyr
branch than to create and reference a separatezephyr-v6.0.0
branch.Note that merge commits are allowed in the CMSIS-NN module repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What makes more sense is up to the repo maintainer to decide. For the other modules I control I create branches per upstream release, as I see more value in having a clean diff (that is possible to review) from the upsteam release than a linear commit history (e.g. https://github.com/zephyrproject-rtos/loramac-node).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, as long as the maintainer sticks with only one method.
That makes sense; but, that does not seem to be how upstream syncs are meant to be handled for the particular module (especially, looking at the branch name) -- for example, what is the
zephyr
branch supposed to be afterzephyr-v6.0.0
branch is created?If you, as the maintainer of the CMSIS-NN module, decide to do this, it would only make sense to rename the existing
zephyr
branch accordingly.On a side note, maybe we need a place to properly document how every module handles upstream syncs so that we do not end up with a mess like
zephyr
,zephyr-v2.6
andv4.7.0-zephyr
, as seen in theloramac-node
module repository.