From: Borislav Petkov <bp@alien8.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Chiawen Huang <chiawen.huang@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Alex Deucher <alexander.deucher@amd.com>,
Tony Cheng <Tony.Cheng@amd.com>
Subject: Re: 8353d30e747f ("drm/amd/display: disable stream if pixel clock changed with link active")
Date: Tue, 15 Dec 2020 19:43:06 +0100 [thread overview]
Message-ID: <20201215184306.GD9817@zn.tnic> (raw)
In-Reply-To: <CADnq5_N=CiuGKe4V-4a8s=SEAR9M4W8X_vdshgbwXH2b9u+L2g@mail.gmail.com>
On Tue, Dec 15, 2020 at 12:04:23PM -0500, Alex Deucher wrote:
> That patch trivially backports to 5.10. See attached backported
> patch. @Borislav Petkov does the attached patch fix 5.10 for you?
Yes, thanks.
Reported-and-tested-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Tony Cheng <Tony.Cheng@amd.com>,
Chiawen Huang <chiawen.huang@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: 8353d30e747f ("drm/amd/display: disable stream if pixel clock changed with link active")
Date: Tue, 15 Dec 2020 19:43:06 +0100 [thread overview]
Message-ID: <20201215184306.GD9817@zn.tnic> (raw)
In-Reply-To: <CADnq5_N=CiuGKe4V-4a8s=SEAR9M4W8X_vdshgbwXH2b9u+L2g@mail.gmail.com>
On Tue, Dec 15, 2020 at 12:04:23PM -0500, Alex Deucher wrote:
> That patch trivially backports to 5.10. See attached backported
> patch. @Borislav Petkov does the attached patch fix 5.10 for you?
Yes, thanks.
Reported-and-tested-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-12-15 18:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 15:55 8353d30e747f ("drm/amd/display: disable stream if pixel clock changed with link active") Borislav Petkov
2020-12-11 15:55 ` Borislav Petkov
2020-12-14 21:49 ` Alex Deucher
2020-12-14 21:49 ` Alex Deucher
2020-12-15 15:49 ` Rodrigo Siqueira
2020-12-15 15:49 ` Rodrigo Siqueira
2020-12-15 15:51 ` Alex Deucher
2020-12-15 15:51 ` Alex Deucher
2020-12-15 15:47 ` Rodrigo Siqueira
2020-12-15 15:47 ` Rodrigo Siqueira
2020-12-15 15:56 ` Borislav Petkov
2020-12-15 15:56 ` Borislav Petkov
2020-12-15 16:07 ` Rodrigo Siqueira
2020-12-15 16:07 ` Rodrigo Siqueira
2020-12-15 16:18 ` Alex Deucher
2020-12-15 16:18 ` Alex Deucher
2020-12-15 16:42 ` Rodrigo Siqueira
2020-12-15 16:42 ` Rodrigo Siqueira
2020-12-15 17:04 ` Alex Deucher
2020-12-15 17:04 ` Alex Deucher
2020-12-15 18:43 ` Borislav Petkov [this message]
2020-12-15 18:43 ` Borislav Petkov
2020-12-15 19:00 ` Rodrigo Siqueira
2020-12-15 19:00 ` Rodrigo Siqueira
2020-12-15 19:07 ` Borislav Petkov
2020-12-15 19:07 ` Borislav Petkov
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=20201215184306.GD9817@zn.tnic \
--to=bp@alien8.de \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Tony.Cheng@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chiawen.huang@amd.com \
--cc=linux-kernel@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.