On Thu, 24 Jul 2025, Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> wrote: > Em Thu, 24 Jul 2025 08:42:59 -0600 > Jonathan Corbet <corbet@xxxxxxx> escreveu: > >> Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> writes: >> >> > Maybe I can place instead CONFIG_DRM_I915_WERROR. >> >> I've held off on this series on the expectation that a new version would >> come. I guess, at this point, it will be a post-merge-window thing? > > Feel free to postpone. I have already a new version of it here somewhere on > my branches, but I had to take some days off. So, I ended not sending you > the (probably) final version. > > I intend to send what I have here during the merge window for you to > review and apply post-merge-window. I think the main questions here are 1) how to handle optional build tool dependencies, and 2) whether Python is an optional or required dependency. It might be nice to be able to have an actual Kconfig and dependency for optional tools. "depends on TOOL_PYTHON" or something. Enable the option, and you should have Python. This in turn raises the question for allyesconfig. It's cumbersome (though not impossible) to add config options that you actually have to enable manually. The header test stuff really isn't required to actually build the kernel or drm, however DRM_MSM does depend on Python for building the driver. BR, Jani. -- Jani Nikula, Intel
