mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aditya Garg <gargaditya08@live.com>
To: Harry Wentland <hwentlan@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
	"harry.wentland@amd.com" <harry.wentland@amd.com>,
	"sunpeng.li@amd.com" <sunpeng.li@amd.com>,
	"Rodrigo.Siqueira@amd.com" <Rodrigo.Siqueira@amd.com>,
	"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
	"christian.koenig@amd.com" <christian.koenig@amd.com>,
	"Xinhui.Pan@amd.com" <Xinhui.Pan@amd.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Felix.Kuehling@amd.com" <Felix.Kuehling@amd.com>,
	"evan.quan@amd.com" <evan.quan@amd.com>,
	"stylon.wang@amd.com" <stylon.wang@amd.com>,
	"wesley.chalmers@amd.com" <wesley.chalmers@amd.com>,
	"qingqing.zhuo@amd.com" <qingqing.zhuo@amd.com>,
	"George.Shen@amd.com" <George.Shen@amd.com>,
	"roman.li@amd.com" <roman.li@amd.com>,
	"solomon.chiu@amd.com" <solomon.chiu@amd.com>,
	"Aurabindo.Pillai@amd.com" <Aurabindo.Pillai@amd.com>,
	"wayne.lin@amd.com" <wayne.lin@amd.com>,
	"mikita.lipski@amd.com" <mikita.lipski@amd.com>,
	"Bhawanpreet.Lakha@amd.com" <Bhawanpreet.Lakha@amd.com>,
	"agustin.gutierrez@amd.com" <agustin.gutierrez@amd.com>,
	"pavle.kotarac@amd.com" <pavle.kotarac@amd.com>,
	Aun-Ali Zaidi <admin@kodeit.net>,
	Orlando Chamberlain <redecorating@protonmail.com>
Subject: Re: [PATCH RESEND] drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple Retina panels
Date: Sat, 29 Jan 2022 05:48:38 +0000	[thread overview]
Message-ID: <0128D2BE-EB65-4E9E-B8C0-33DFE8D20CBC@live.com> (raw)
In-Reply-To: <0932bbf6-409e-0d3e-2824-b33914033f81@amd.com>



> On 28-Jan-2022, at 8:33 PM, Harry Wentland <hwentlan@amd.com> wrote:
> 
> I think either leaving the 2017 quirk in its original place or moving it down works. I don't have a strong preference.
I’d better leave it in the original place then
> 
> With the comment style addressed this patch is
Sending a v2 now with this issue addressed.
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
> 
> Harry



  reply	other threads:[~2022-01-29  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 11:31 Aditya Garg
2022-01-27 17:36 ` Alex Deucher
2022-01-28 13:06   ` Aditya Garg
2022-01-28 15:03     ` Harry Wentland
2022-01-29  5:48       ` Aditya Garg [this message]
2022-01-29  5:49       ` [PATCH v2] " Aditya Garg
2022-01-31 20:17         ` Alex Deucher

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=0128D2BE-EB65-4E9E-B8C0-33DFE8D20CBC@live.com \
    --to=gargaditya08@live.com \
    --cc=Aurabindo.Pillai@amd.com \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=George.Shen@amd.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=admin@kodeit.net \
    --cc=agustin.gutierrez@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=evan.quan@amd.com \
    --cc=harry.wentland@amd.com \
    --cc=hwentlan@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikita.lipski@amd.com \
    --cc=pavle.kotarac@amd.com \
    --cc=qingqing.zhuo@amd.com \
    --cc=redecorating@protonmail.com \
    --cc=roman.li@amd.com \
    --cc=solomon.chiu@amd.com \
    --cc=stylon.wang@amd.com \
    --cc=sunpeng.li@amd.com \
    --cc=wayne.lin@amd.com \
    --cc=wesley.chalmers@amd.com \
    /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

all inboxes | Powered by JetHome®