-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Formatting: Further refinement to dts-linter #100247
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
base: main
Are you sure you want to change the base?
Formatting: Further refinement to dts-linter #100247
Conversation
9739668 to
ffa372f
Compare
ffa372f to
ccc450c
Compare
bjarki-andreasen
left a comment
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.
Looks good
|
I have been doing some testing and found some corner cases in the Linux DST files that the linter will choke on. I have fix most of these but I am not convinced we should merge this in with the DTS linter 0.3.7.... Hence I converted this PR to draft until I release the linter to address these issues. Hopefully I will release new linter later this week UPDATE Issues have been addressed and verified on Linux DTS and Zephyr files. Linter has been released with hotfix2 tag. |
The PR: - Ensure that properties have 2 new lines when node is above it. - Enures that 1 new line is required between a node and #if/#ifdef... - Enures that 2 new line are required between #endif and node. - Wraps property values that exceed 100 characters in length. These chnages need dts-linter version 0.3.7-hotfix2 dts-linter 0.3.7-hotfix2 also addresses - Update `glob` to address CVE-2025-64756 - Update `js-yaml` to address CVE-2025-64718 Signed-off-by: Kyle Bonnici <kylebonnici@hotmail.com>
ccc450c to
2a1afd7
Compare
|



The PR:
These chnages need dts-linter version 0.3.7-hotfix2
dts-linter 0.3.7-hotfix2 also addresses
globto address CVE-2025-64756js-yamlto address CVE-2025-64718