Repository navigation
trusty: ipc: use the current trace string assignment API - #231
Merged
derekross merged 1 commit intoNov 9, 2026
Merged
Conversation
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>
7 tasks done
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
marked this pull request as ready for review
November 9, 2026 16:02
Owner
|
Thanks, Chris. Merging this one. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.