From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Lin, Wayne" <Wayne.Lin@amd.com>
Cc: "lyude@redhat.com" <lyude@redhat.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] drm/dp_mst: Avoid to mess up payload table by ports in stale" failed to apply to 5.13-stable tree
Date: Thu, 15 Jul 2021 19:27:48 +0200 [thread overview]
Message-ID: <YPBwFGmNN2zLb3cf@kroah.com> (raw)
In-Reply-To: <CO6PR12MB548978A31FF543E2333447FFFC129@CO6PR12MB5489.namprd12.prod.outlook.com>
On Thu, Jul 15, 2021 at 03:07:19PM +0000, Lin, Wayne wrote:
> [AMD Official Use Only]
>
> Hi Greg,
>
> Really thanks for your time. About failing to apply below patches to stable tree:
> 3769e4c0af5b82c8ea21d037013cb9564dfaa51f
> [PATCH] drm/dp_mst: Avoid to mess up payload table by ports in stale topology
>
> 35d3e8cb35e75450f87f87e3d314e2d418b6954b
> [PATCH] drm/dp_mst: Do not set proposed vcpi directly
>
> There was an immediate following patch to correct the issue caused by above patches:
> 24ff3dc18b99c4b912ab1746e803ddb3be5ced4c
> [PATCH] drm/dp_mst: Add missing drm parameters to recently added call to drm_dbg_kms()
>
> In other words, these three patches should be committed at the same time. Sorry for any inconvenience it brought.
> Please advise me if there is anything else to do for having these patches applied to stable tree.
> Really thanks for your help.
These commits do not apply to the current stable trees, so please submit
backports of them for how ever far back you wish to see them, so that we
can apply them.
thanks,
greg k-h
next prev parent reply other threads:[~2021-07-15 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 12:17 FAILED: patch "[PATCH] drm/dp_mst: Avoid to mess up payload table by ports in stale" failed to apply to 5.13-stable tree gregkh
2021-07-15 15:07 ` Lin, Wayne
2021-07-15 17:27 ` gregkh [this message]
2021-07-16 2:00 ` Lin, Wayne
-- strict thread matches above, loose matches on Subject: below --
2021-07-15 12:17 gregkh
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=YPBwFGmNN2zLb3cf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Wayne.Lin@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox