public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>, Juston Li <juston.li@intel.com>,
	Lyude <cpaul@redhat.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [RESEND PATCH v2 1/2] drm/dp/mst: Reprobe EDID for MST ports on resume
Date: Fri, 14 Jun 2019 21:56:43 +0000	[thread overview]
Message-ID: <20190614215644.8F9D821874@mail.kernel.org> (raw)
In-Reply-To: <20181024021925.27026-2-juston.li@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

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

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-06-14 21:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  2:19 [RESEND PATCH v2 0/2] Check MST topology change on resume Juston Li
2018-10-24  2:19 ` [RESEND PATCH v2 1/2] drm/dp/mst: Reprobe EDID for MST ports " Juston Li
2018-10-24 22:09   ` Lyude Paul
2018-10-24 22:45     ` Li, Juston
2018-11-09  0:43       ` Lyude Paul
2018-11-26 21:53         ` Li, Juston
2018-11-26 22:35           ` Lyude Paul
2018-10-24 23:02     ` Lyude Paul
2019-06-14 21:56   ` Sasha Levin
2019-06-14 21:56   ` Sasha Levin [this message]
2019-06-14 22:10     ` Lyude Paul
2019-06-15 22:38       ` Sasha Levin
2018-10-24  2:19 ` [RESEND PATCH v2 2/2] drm/i915/mst: Reset MST after resume when necessary Juston Li
2018-10-24  2:48 ` ✗ Fi.CI.BAT: failure for Check MST topology change on resume Patchwork
2018-10-24  8:57 ` [Intel-gfx] [RESEND PATCH v2 0/2] " Daniel Vetter
2018-10-24 16:37   ` Li, Juston

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=20190614215644.8F9D821874@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=cpaul@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=juston.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox