Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Peichen Huang <peichen.huang@amd.com>
Subject: Re: [PATCH 6.1.y] drm/amd/display: limit DPIA link rate to HBR3
Date: Wed, 9 Aug 2023 06:18:23 -0500	[thread overview]
Message-ID: <c85fa930-65e8-47e2-ade6-001566fe9f88@amd.com> (raw)
In-Reply-To: <2023080911-shortage-slicing-6ef8@gregkh>

On 8/9/23 04:05, Greg KH wrote:
> On Mon, Aug 07, 2023 at 09:00:47AM -0500, Mario Limonciello wrote:
>> From: Peichen Huang <peichen.huang@amd.com>
>>
>> [Why]
>> DPIA doesn't support UHBR, driver should not enable UHBR
>> for dp tunneling
>>
>> [How]
>> limit DPIA link rate to HBR3
>>
>> Cc: Mario Limonciello <mario.limonciello@amd.com>
>> Cc: Alex Deucher <alexander.deucher@amd.com>
>> Cc: stable@vger.kernel.org
>> Acked-by: Stylon Wang <stylon.wang@amd.com>
>> Signed-off-by: Peichen Huang <peichen.huang@amd.com>
>> Reviewed-by: Mustapha Ghaddar <Mustapha.Ghaddar@amd.com>
>> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>> (cherry picked from commit 0e69ef6ea82e8eece7d2b2b45a0da9670eaaefff)
>> This was CC to stable, but failed to apply because the file was
>> renamed in 6.3-rc1 as part of
>> 54618888d1ea ("drm/amd/display: break down dc_link.c")
> 
> It also is not in 6.4.y, why not?  I can't take it for 6.1.y only,
> otherwise people will have a regression when they move to a new kernel.
> 
> thanks,
> 
> greg k-h

This is one of those cases that the same commit landed in the tree twice 
as two hashes.

Here's the 6.4 hash (which is identical):

$ git describe --contains 7c5835bcb9176df94683396f1c0e5df6bf5094b3
v6.4-rc7~9^2~2^2

  reply	other threads:[~2023-08-09 11:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 14:00 [PATCH 6.1.y] drm/amd/display: limit DPIA link rate to HBR3 Mario Limonciello
2023-08-09  9:05 ` Greg KH
2023-08-09 11:18   ` Mario Limonciello [this message]
2023-08-12  6:01     ` Greg KH

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=c85fa930-65e8-47e2-ade6-001566fe9f88@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=peichen.huang@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