For context, see:
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1135724
It seems that we keep reenabling FB_* modules, which uses memory and can potentially expose and API which we don't support.
There is an existing kernel test (kernel_ConfigVerify.py) and we could model something after it ("graphics_KernelConfig") which checks that the FB_* options are not enabled by mistake.
Comment 1 by marc...@chromium.org
, Jul 18Owner: pwang@chromium.org
Status: Assigned (was: Untriaged)