All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: Prike.Liang@amd.com, alexander.deucher@amd.com,
	evan.quan@amd.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/amd/powerplay: map mclk to fclk for COMBINATIONAL_BYPASS" failed to apply to 5.5-stable tree
Date: Mon, 9 Mar 2020 20:27:44 -0400	[thread overview]
Message-ID: <20200310002744.GC24841@sasha-vm> (raw)
In-Reply-To: <158378236575229@kroah.com>

On Mon, Mar 09, 2020 at 08:32:45PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.5-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 ab65a371dd5f5cba6bd9a58a1a6d4115a71cc5c9 Mon Sep 17 00:00:00 2001
>From: Prike Liang <Prike.Liang@amd.com>
>Date: Wed, 4 Mar 2020 10:36:21 +0800
>Subject: [PATCH] drm/amd/powerplay: map mclk to fclk for COMBINATIONAL_BYPASS
> case
>
>When hit COMBINATIONAL_BYPASS the mclk will be bypass and can export
>fclk frequency to user usage.
>
>Signed-off-by: Prike Liang <Prike.Liang@amd.com>
>Reviewed-by: Evan Quan <evan.quan@amd.com>
>Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>Cc: stable@vger.kernel.org

Is it actually needed anywhere without 0b97bd6cde1d ("drm/amd/powerplay:
implement interface to retrieve clock freq for renoir")?

-- 
Thanks,
Sasha

  reply	other threads:[~2020-03-10  0:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09 19:32 FAILED: patch "[PATCH] drm/amd/powerplay: map mclk to fclk for COMBINATIONAL_BYPASS" failed to apply to 5.5-stable tree gregkh
2020-03-10  0:27 ` Sasha Levin [this message]
2020-03-10  0:44   ` Liang, Prike

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=20200310002744.GC24841@sasha-vm \
    --to=sashal@kernel.org \
    --cc=Prike.Liang@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=evan.quan@amd.com \
    --cc=gregkh@linuxfoundation.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 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.