lopper_lib.py: Restrict cpu_refs to direct CPU child nodes#714
Merged
zeddii merged 1 commit intodevicetree-org:masterfrom Mar 13, 2026
Merged
lopper_lib.py: Restrict cpu_refs to direct CPU child nodes#714zeddii merged 1 commit intodevicetree-org:masterfrom
zeddii merged 1 commit intodevicetree-org:masterfrom
Conversation
The cpu_refs helper was previously searching for any "cpu@*" subnode under a CPU node using a path-based match. That could accidentally pick up nested cache nodes or other children whose paths include "cpu@", which leads to spurious CPU references in the aggregate list. By switching to a child-only lookup, we now only consider direct CPU children of the target node and ignore nested descendants. Examples: - Before: /cpus/cpu@0/l2-cache/cpu@* could be matched as a CPU - After: only /cpus/cpu@* direct children are collected
kedareswararao
approved these changes
Mar 13, 2026
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
3 participants
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.
The cpu_refs helper was previously searching for any "cpu@*" subnode under a CPU node using a path-based match. That could accidentally pick up nested cache nodes or other children whose paths include "cpu@", which leads to spurious CPU references in the aggregate list.
By switching to a child-only lookup, we now only consider direct CPU children of the target node and ignore nested descendants.
Examples: