Skip to content

trusty: ipc: use the current trace string assignment API - #231

Merged
derekross merged 1 commit into
derekross:omamobilefrom
latentoperator:omamobile-trusty-trace-api
Nov 9, 2026
Merged

derekross merged 1 commit into
derekross:omamobilefrom
latentoperator:omamobile-trusty-trace-api

Conversation

@latentoperator

@latentoperator latentoperator commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Use the current one-argument __assign_str API in Trusty IPC's trace events. The declared source expressions stay unchanged. This fixes the build when tracing is enabled; no Trusty runtime or storage proxy was exercised on Bluejay.

Validation: explicit W=1 Trusty IPC object compilation passed during preparation; the submitted signed head 635c527 passes kernel CI. The existing author DCO remains verified and no source changed while marking ready. Ready for review at the maintainer's invitation on November 9. This change is independent of the other Bluejay development topics.

The current trace macro accepts only the field name. Keep the
integration tree buildable by using that API. This is a build
compatibility change; no Trusty runtime was exercised on Bluejay.

Assisted-by: LLM
Signed-off-by: Chris Gray <chrisgray70@gmail.com>
@derekross

Copy link
Copy Markdown
Owner

Thank you, Chris — this is right: the two-argument form only builds today because our release config has tracing off. Happy to take it; please mark it ready when you are.

@latentoperator
latentoperator marked this pull request as ready for review November 9, 2026 16:02
@derekross

Copy link
Copy Markdown
Owner

Thanks, Chris. Merging this one.

@derekross
derekross merged commit abcd6aa into derekross:omamobile Nov 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants