-
Notifications
You must be signed in to change notification settings - Fork 159
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
Add an add_x86_only_kconfig_checks and an add_arm_only_kconfig_checks function #128
base: master
Are you sure you want to change the base?
Conversation
… function Splitting the checks by arch family makes the code a tad more readable and self-contains, and makes it easier to inspect what checks are architecture-specific, instead of having the read the whole file.
Is this something you're interested in @a13xp0p0v? Otherwise, I won't spend time resolving conflicts :) |
ea24300
to
78f5595
Compare
Hello @jvoisin, This branch breaks the current order of the checks. Let me describe the rationale, maybe we will create a better solution. First, all checks in
In each
In each
This ordering of the checks in We also discussed this with @asarubbo in #113. Does it sound reasonable? |
I think it depends what we want to optimize for, code-wise: do we think it's easier to group checks by reason, or by architecture. I think the latter is more desirable, grouping by reason also makes sense. What would be nice would be to actually group the checks, either in |
By the way, I guess this refactoring will allow to do easy alphabetical sorting inside each group. |
That's the plan :> |
It's a big and important refactoring. |
Splitting the checks by arch family makes the code a tad more readable and self-contains, and makes it easier to inspect what checks are architecture-specific, instead of having the read the whole file.