-
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
Put the id field at the end of the psa_key_attributes_s structure #8745
Conversation
Putting the id at the of the psa_key_attributes_s structure allows for a more efficient marshalling of the parameters around a transport channel which provides separation between a client view and a service view of the key parameters. Signed-off-by: Antonio de Angelis <antonio.deangelis@arm.com>
This breaks ABI as it's re-arranging the fields of the structures. The new layout could be put under |
The ABI change is fine outside of an LTS. We explicitly mention re-ordering fields as OK in |
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
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.
Ok but needs comments.
Make sure the layout of psa_key_attributes_s is commented enough so that it does not accidentally get reorganized by mistake in the future. Signed-off-by: Antonio de Angelis <antonio.deangelis@arm.com>
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 apart from the macro name
Signed-off-by: Antonio de Angelis <antonio.deangelis@arm.com>
6932e29
Fixed. |
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
Description
Putting the
id
at the of thepsa_key_attributes_s
structure allows for a more efficient marshalling of the parameters around a transport channel which provides separation between a client view and a service view of the key parameters.PR checklist