Re: FAILED - [PATCH v2 3/3] drm/mgag200: Add workaround for HW that does not support 'startadd'
Hello Sasha and Thomas ,
This particular patch has failed on one class of servers that has a slightly different Sun Vendor. ID for the BMC video device:
I will follow up with additional details in the review comments for the original message,.
On Nov 28, 2019, at 8:23 AM, Sasha Levin sashal@kernel.org wrote:
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag, fixing commit: 81da87f63a1e ("drm: Replace drm_gem_vram_push_to_system() with kunmap + unpin").
The bot has tested the following trees: v5.3.13.
v5.3.13: Build failed! Errors: drivers/gpu/drm/mgag200/mgag200_drv.c:104:18: error: ‘drm_vram_mm_debugfs_init’ undeclared here (not in a function); did you mean ‘drm_client_debugfs_init’?
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
-- Thanks, Sasha _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_m...
On Dec 3, 2019, at 11:30 AM, John Donnelly john.p.donnelly@oracle.com wrote:
Hello Sasha and Thomas ,
This particular patch has failed on one class of servers that has a slightly different Sun Vendor. ID for the BMC video device:
I will follow up with additional details in the review comments for the original message,.
On Nov 28, 2019, at 8:23 AM, Sasha Levin sashal@kernel.org wrote:
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag, fixing commit: 81da87f63a1e ("drm: Replace drm_gem_vram_push_to_system() with kunmap + unpin").
The bot has tested the following trees: v5.3.13.
v5.3.13: Build failed! Errors: drivers/gpu/drm/mgag200/mgag200_drv.c:104:18: error: ‘drm_vram_mm_debugfs_init’ undeclared here (not in a function); did you mean ‘drm_client_debugfs_init’?
I had this same issue and removed that from my local 5.4.0-rc8 build
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
-- Thanks, Sasha _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_m...
Hi
Am 06.12.19 um 01:48 schrieb John Donnelly:
On Dec 3, 2019, at 11:30 AM, John Donnelly john.p.donnelly@oracle.com wrote:
Hello Sasha and Thomas ,
This particular patch has failed on one class of servers that has a slightly different Sun Vendor. ID for the BMC video device:
I will follow up with additional details in the review comments for the original message,.
On Nov 28, 2019, at 8:23 AM, Sasha Levin sashal@kernel.org wrote:
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag, fixing commit: 81da87f63a1e ("drm: Replace drm_gem_vram_push_to_system() with kunmap + unpin").
The bot has tested the following trees: v5.3.13.
v5.3.13: Build failed! Errors: drivers/gpu/drm/mgag200/mgag200_drv.c:104:18: error: ‘drm_vram_mm_debugfs_init’ undeclared here (not in a function); did you mean ‘drm_client_debugfs_init’?
I had this same issue and removed that from my local 5.4.0-rc8 build
The bot used the wrong tree. The patch has been written against drm-tip.
Best regards Thomas
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
-- Thanks, Sasha _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_m...
dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
linux-stable-mirror@lists.linaro.org
-
John Donnelly -
Thomas Zimmermann