uh, Sasha not sure if you're a bot or not but this patch isn't even upstream
On Fri, 2019-06-14 at 21:56 +0000, Sasha Levin wrote:
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.1.9, v4.19.50, v4.14.125, v4.9.181, v4.4.181.
v5.1.9: Build failed! Errors: drivers/gpu/drm/drm_dp_mst_topology.c:2672:9: error: implicit declaration of function ‘drm_dp_get_validated_port_ref’; did you mean ‘drm_mode_validate_driver’? [-Werror=implicit-function-declaration] drivers/gpu/drm/drm_dp_mst_topology.c:2676:9: error: implicit declaration of function ‘drm_dp_get_validated_mstb_ref’; did you mean ‘drm_mode_validate_size’? [-Werror=implicit-function-declaration] drivers/gpu/drm/drm_dp_mst_topology.c:2684:3: error: implicit declaration of function ‘drm_dp_put_mst_branch_device’; did you mean ‘drm_dp_get_mst_branch_device’? [-Werror=implicit-function-declaration] drivers/gpu/drm/drm_dp_mst_topology.c:2715:2: error: implicit declaration of function ‘drm_dp_put_port’; did you mean ‘drm_dp_get_port’? [-Werror=implicit-function-declaration]
v4.19.50: Build OK! v4.14.125: Build OK! v4.9.181: Build OK! v4.4.181: Build OK!
How should we proceed with this patch?
-- Thanks, Sasha
On Fri, Jun 14, 2019 at 06:10:20PM -0400, Lyude Paul wrote:
uh, Sasha not sure if you're a bot or not but this patch isn't even upstream
This is indeed a bot, and that's indeed it's purpose :)
We tend to get less responses if we wait for weeks for a patch to get upstream and queued for -stable because most often folks have moved on and forgotten all about it.
This bot looks for commits tagged for stable, and runs basic sanity checks on them while they're still being discussed on the mailing list. This way we get more responses with instructions on how to deal with the patch.
Either way, it won't be actually queued for stable before it's upstream.
-- Thanks, Sasha
linux-stable-mirror@lists.linaro.org