-
Notifications
You must be signed in to change notification settings - Fork 2.1k
drivers/mtd: fix Kconfig dependencies #16836
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
Merged
Merged
Conversation
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
fjmolinas
commented
Sep 13, 2021
@leandrolanzieri murdock is green, do you still have concerns? |
No, I think the changes are good! Please squash |
Currently implementations of the MTD api are selecting the module, this makes it easy for default backends to be selected. But the correct modeling is simply selecting the MTD api and then selecting a backend. BOARDs providing one of the backends can expose this and then that backend can be selected by default. There is also currently nothing preventing from using the MTD api with no backend since a mock backend can easily be provided as is done in all mtd tests.
5761386
to
14ef09b
Compare
leandrolanzieri
approved these changes
Sep 22, 2021
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.
ACK!
go! |
Thanks for the review @leandrolanzieri! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: cpu
Area: CPU/MCU ports
Area: drivers
Area: Device drivers
Area: Kconfig
Area: Kconfig integration
Area: tests
Area: tests and testing framework
CI: ready for build
If set, CI server will compile all applications for all available boards for the labeled PR
Platform: native
Platform: This PR/issue effects the native platform
Reviewed: 1-fundamentals
The fundamentals of the PR were reviewed according to the maintainer guidelines
Reviewed: 2-code-design
The code design of the PR was reviewed according to the maintainer guidelines
Reviewed: 3-testing
The PR was tested according to the maintainer guidelines
Reviewed: 4-code-style
The adherence to coding conventions by the PR were reviewed according to the maintainer guidelines
Reviewed: 5-documentation
The documentation details of the PR were reviewed according to the maintainer guidelines
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.
Contribution description
Currently, implementations of the MTD api are selecting the module,
this makes it easy for default backends to be selected. But the
correct modeling is simply selecting the MTD api and then selecting
a backend. BOARDs providing one of the backends can expose this and
then that backend can be selected by default.
There is also currently nothing preventing from using the MTD api
with no backend since a mock backend can easily be provided as is
done in all mtd tests.
Testing procedure
tests/mtd_raw
Issues/PRs references
Split out of #16780