From: John Donnelly <john.p.donnelly@oracle.com>
To: Sasha Levin <sashal@kernel.org>
Cc: "Thomas Zimmermann" <tzimmermann@suse.de>,
airlied@redhat.com, daniel@ffwll.ch, stable@vger.kernel.org,
"Neil Armstrong" <narmstrong@baylibre.com>,
"David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
"Gerd Hoffmann" <kraxel@redhat.com>,
"José Roberto de Souza" <jose.souza@intel.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andrzej Pietrasiewicz" <andrzej.p@collabora.com>,
"Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: FAILED - [PATCH v2 3/3] drm/mgag200: Add workaround for HW that does not support 'startadd'
Date: Tue, 3 Dec 2019 11:30:50 -0600 [thread overview]
Message-ID: <53967A49-E729-409B-8FDD-019160FFF675@oracle.com> (raw)
In-Reply-To: <20191128142337.1B32A217F5@mail.kernel.org>
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_mailman_listinfo_dri-2Ddevel&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=vxMDOLV77rRe2ekdNFH9IxMSBQrTccltZd8A1H6xYCc&s=efHs2lc_RQYvzLC82c-D3wa8MpX5DCU_YsIo6XruAQg&e=
next prev parent reply other threads:[~2019-12-03 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191126101529.20356-1-tzimmermann@suse.de>
2019-11-26 10:15 ` [PATCH v2 1/3] drm/mgag200: Extract device type from flags Thomas Zimmermann
2019-11-27 16:29 ` Emil Velikov
2019-11-27 18:08 ` Thomas Zimmermann
2019-11-28 12:46 ` Emil Velikov
2019-11-26 10:15 ` [PATCH v2 2/3] drm/mgag200: Store flags from PCI driver data in device structure Thomas Zimmermann
2019-11-26 10:15 ` [PATCH v2 3/3] drm/mgag200: Add workaround for HW that does not support 'startadd' Thomas Zimmermann
[not found] ` <20191128142337.1B32A217F5@mail.kernel.org>
2019-12-03 17:30 ` John Donnelly [this message]
2019-12-06 0:48 ` FAILED - " John Donnelly
2019-12-06 6:02 ` Thomas Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53967A49-E729-409B-8FDD-019160FFF675@oracle.com \
--to=john.p.donnelly@oracle.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=andrzej.p@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=kraxel@redhat.com \
--cc=narmstrong@baylibre.com \
--cc=sam@ravnborg.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).