From: Justin M. Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2832#note_1682054528 I don't see why we would be using custom-overrides for this at all. If it is hardware that does not exist on x86, we should be disabling the config there. We have an issue that many of these drivers are written for an upstream chip, but when they are merged to the kernel, we don't know what hardware they will actually end up in. We have been turning them on if they are a vendor which typically supplies to x86 board or pc manufacturers, so that if they do use that part in a future product, it is supported. This does make for a nice end user experience as more things are supported on release, but it does present a problem that we have a large number of drivers enabled as modules which serve no purpose in the real world. I like the problem that this is trying to solve, I just want to know where it is getting the data to do so, and how that data is maintained. -- _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
