From: Lyude Paul <lyude@redhat.com>
To: Sasha Levin <Alexander.Levin@microsoft.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Gustavo Padovan <gustavo@padovan.org>
Subject: Re: [PATCH 1/6] drm/dp_mst: Introduce drm_dp_mst_connector_atomic_check()
Date: Wed, 19 Sep 2018 18:00:55 -0400 [thread overview]
Message-ID: <4a074cc77b180bc16f3356012152451bfbf3bffa.camel@redhat.com> (raw)
In-Reply-To: <CY4PR21MB0776A3CBF3A154B174C2DCD2FB1C0@CY4PR21MB0776.namprd21.prod.outlook.com>
On Wed, 2018-09-19 at 18:58 +0000, Sasha Levin wrote:
> 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: v4.18.8, v4.14.70, v4.9.127, v4.4.156,
> v3.18.122,
>
> v4.18.8: Build OK!
> v4.14.70: Build OK!
> v4.9.127: Failed to apply! Possible dependencies:
> 3f3353b7e121 ("drm/dp: Introduce MST topology state to track available
> link bandwidth")
> edb1ed1ab7d3 ("drm/dp: Add DP MST helpers to atomically find and release
> vcpi slots")
>
> v4.4.156: Failed to apply! Possible dependencies:
> 3f3353b7e121 ("drm/dp: Introduce MST topology state to track available
> link bandwidth")
> edb1ed1ab7d3 ("drm/dp: Add DP MST helpers to atomically find and release
> vcpi slots")
>
> v3.18.122: Failed to apply! Possible dependencies:
> 3f3353b7e121 ("drm/dp: Introduce MST topology state to track available
> link bandwidth")
> edb1ed1ab7d3 ("drm/dp: Add DP MST helpers to atomically find and release
> vcpi slots")
>
>
> Please let us know how to resolve this.
...is this the email address I'm supposed to "let you know how to resolve this"
with? if that is the case, it's 100% OK to simply ignore all of the versions
that don't apply with this patch.
>
> --
> Thanks,
> Sasha
next prev parent reply other threads:[~2018-09-20 3:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180918230637.20700-1-lyude@redhat.com>
2018-09-18 23:06 ` [PATCH 1/6] drm/dp_mst: Introduce drm_dp_mst_connector_atomic_check() Lyude Paul
2018-09-19 18:58 ` Sasha Levin
2018-09-19 22:00 ` Lyude Paul [this message]
2018-09-20 9:16 ` Dan Carpenter
2018-09-20 23:35 ` Harry Wentland
2018-09-18 23:06 ` [PATCH 2/6] drm/nouveau: Unbreak nv50_mstc->best_encoder() Lyude Paul
2018-09-18 23:06 ` [PATCH 3/6] drm/i915: Leave intel_conn->mst_port set, use mst_port_gone instead Lyude Paul
2018-09-19 18:58 ` Sasha Levin
2018-09-19 22:01 ` Lyude Paul
2018-09-21 9:27 ` [Intel-gfx] " Daniel Vetter
2018-09-21 20:17 ` Lyude Paul
2018-09-22 8:51 ` Daniel Vetter
2018-09-18 23:06 ` [PATCH 4/6] drm/i915: Skip vcpi allocation for MSTB ports that are gone Lyude Paul
2018-09-18 23:06 ` [PATCH 5/6] drm/i915: Fix intel_dp_mst_best_encoder() 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=4a074cc77b180bc16f3356012152451bfbf3bffa.camel@redhat.com \
--to=lyude@redhat.com \
--cc=Alexander.Levin@microsoft.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=nouveau@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).