From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: mario.kleiner.de@gmail.com, alexander.deucher@amd.com,
harry.wentland@amd.com, martin.leung@amd.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/amd/display: Reorder detect_edp_sink_caps before link" failed to apply to 5.4-stable tree
Date: Sun, 19 Jan 2020 11:18:30 -0500 [thread overview]
Message-ID: <20200119161829.GT1706@sasha-vm> (raw)
In-Reply-To: <157944472417561@kroah.com>
On Sun, Jan 19, 2020 at 03:38:44PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.4-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 3b7c59754cc22760760a84ebddb8e0b1e8dd871b Mon Sep 17 00:00:00 2001
>From: Mario Kleiner <mario.kleiner.de@gmail.com>
>Date: Thu, 9 Jan 2020 16:20:27 +0100
>Subject: [PATCH] drm/amd/display: Reorder detect_edp_sink_caps before link
> settings read.
>
>read_current_link_settings_on_detect() on eDP 1.4+ may use the
>edp_supported_link_rates table which is set up by
>detect_edp_sink_caps(), so that function needs to be called first.
>
>Reviewed-by: Harry Wentland <harry.wentland@amd.com>
>Signed-off-by: Mario Kleiner <mario.kleiner.de@gmail.com>
>Cc: Martin Leung <martin.leung@amd.com>
>Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>Cc: stable@vger.kernel.org
Context conflicts due to missing 7f7652ee8c8c ("drm/amd/display: enable
single dp seamless boot"). Fixed up and queued for 5.4 and 4.19.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-01-19 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 14:38 FAILED: patch "[PATCH] drm/amd/display: Reorder detect_edp_sink_caps before link" failed to apply to 5.4-stable tree gregkh
2020-01-19 16:18 ` Sasha Levin [this message]
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=20200119161829.GT1706@sasha-vm \
--to=sashal@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=harry.wentland@amd.com \
--cc=mario.kleiner.de@gmail.com \
--cc=martin.leung@amd.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