Hej,
On Mon, May 5, 2025, at 10:49, Greg Kroah-Hartman wrote:
On Mon, May 05, 2025 at 10:33:49AM +0200, Janne Grunau wrote:
Hej,
On Mon, May 5, 2025, at 09:53, gregkh@linuxfoundation.org wrote:
The patch below does not apply to the 6.6-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to stable@vger.kernel.org.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.6.y git checkout FETCH_HEAD git cherry-pick -x 32dce6b1949a696dc7abddc04de8cbe35c260217
This works for me without conflicts. Are there git configs which might influence this? The only noticeable thing is that the position of the DRM_DEBUG_DP_MST_TOPOLOGY_REFS entry shifted 82 lines down. I looked at the history of drivers/gpu/drm/Kconfig and the config DRM_DEBUG_DP_MST_TOPOLOGY_REFS block hasn't changed since v5.10. So I would expect the cherry-pick to work.
It applies cleanly, but breaks the build badly. Try it and see :)
Indeed. The issue is caused by turning CONFIG_DRM_KMS_HELPER from 'm' to 'y' while leaving CONFIG_DRM as 'm'. This is clearly broken and not intended. It's exactly what Documentation/kbuild/kconfig-language.rst warns about. OTOH it also warns about using both 'depends on' and 'select' on the same symbol which blows up here. I don't see which change between in v6.6..v6.12 for scripts/kconfig could have changed this.
Using "select DRM_KMS_HELPER if DRM" fixes the linux-6.6.y build. I only discovered this as possible solution from the commit message of commit 77a92660d8fe ("kconfig: remove wrong expr_trans_bool()").
CC-ing kconfig maintainer for clarification if "select DRM_KMS_HELPER if DRM" is a valid solution for this issue. Commit causing issue replicated below for context.
thanks, Janne