-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Replace references to Mbed Crypto (rebase) #7589
Conversation
…tion and comments. Signed-off-by: Fredrik Hesse <[email protected]>
…tion and comments. Signed-off-by: Fredrik Hesse <[email protected]>
Signed-off-by: Fredrik Hesse <[email protected]>
@AndrzejKurek since you reviewed previously, please could you TAL? @tom-daubney-arm - please could you also review, thanks |
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.
LGTM
@daverodgman If you think one review is enough, you can add (I am on the fence here - it's at the edge of what I feel a single reviewer should approve) |
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.
LGTM (mostly, I checked that we do preserve the historical names in the storage specification)
This needs a 2.28 backport: Mbed TLS 2.28 is not a version of Mbed Crypto. |
@tom-cosgrove-arm single-reviewer is up to the reviewer. The author should stay out of this decision due to an obvious conflict of interest. (I admit I have single-reviewered a PR of mine before, because the reviewers just weren't coming out and oking it even if they did approve. But it shouldn't be that way.) |
It's fine for the author to mark a PR single-reviewer - it's more of a hint coming from the author. The reviewer can always remove that label if they feel a second reviewer is warranted, and the gatekeeper can do the same. |
Description
Rebased version of #4990.
PR checklist
Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new feature")