From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>, Lyude Paul <lyude@redhat.com>,
dri-devel@lists.freedesktop.org
Cc: Jerry Zuo <Jerry.Zuo@amd.com>, stable@vger.kernel.org
Subject: Re: [PATCH] drm/dp_mst: Skip validating ports during destruction, just ref
Date: Thu, 15 Nov 2018 07:06:21 +0000 [thread overview]
Message-ID: <20181115070622.7393C22419@mail.kernel.org> (raw)
In-Reply-To: <20181113224613.28809-1-lyude@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 263efde31f97 drm/dp/mst: Get validated port ref in drm_dp_update_payload_part1().
The bot has tested the following trees: v4.19.2, v4.18.19, v4.14.81, v4.9.137, v4.4.163, v3.18.125.
v4.19.2: Build OK!
v4.18.19: Build OK!
v4.14.81: Build OK!
v4.9.137: Build OK!
v4.4.163: Build OK!
v3.18.125: Build failed! Errors:
drivers/gpu/drm/drm_dp_mst_topology.c:944:6: error: implicit declaration of function ‘current_work’; did you mean ‘current_umask’? [-Werror=implicit-function-declaration]
drivers/gpu/drm/drm_dp_mst_topology.c:944:28: error: ‘struct drm_dp_mst_topology_mgr’ has no member named ‘destroy_connector_work’
--
Thanks,
Sasha
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-11-15 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 22:46 [PATCH] drm/dp_mst: Skip validating ports during destruction, just ref Lyude Paul
2018-11-15 7:06 ` Sasha Levin [this message]
2018-11-21 20:08 ` Dave Airlie
2018-11-21 20:24 ` Lyude Paul
2018-11-22 8:34 ` Daniel Vetter
2018-11-26 20:37 ` Lyude Paul
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=20181115070622.7393C22419@mail.kernel.org \
--to=sashal@kernel.org \
--cc=Jerry.Zuo@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lyude@redhat.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.