drivers: dac: rename max22017 dac binding file to max22017-dac.yaml #84551
Conversation
This file contains 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
Avoid clashing with the existing max22017.yaml binding file used for the MFD. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
kartben
added
the
Hotfix
zephyrbot
added
size: XS
zephyrbot
requested review from
galak,
martinjaeger,
MaureenHelm,
microbuilder,
ozersa and
ttmut
henrikbrixandersen
approved these changes
Jan 25, 2025
ttmut
approved these changes
Jan 25, 2025
pdgendt
approved these changes
Jan 25, 2025
cfriedt
approved these changes
Jan 25, 2025
jhedberg
approved these changes
Jan 25, 2025
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.
Avoid clashing with the existing max22017.yaml binding file used for the MFD.
This is causing scheduled doc build to fail since #76017 was merged (https://github.com/zephyrproject-rtos/zephyr/actions/workflows/doc-build.yml?query=event%3Aschedule)
Longer term fix would be to either enforce naming yaml files same as the compatible (sounds a bit extreme, but after all I believe it's good practice), or make sure that the documentation tooling that generates docs from bindings file is not failing when there are duplicate file names.