From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Stephen Boyd <swboyd@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Guenter Roeck <groeck@chromium.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Vara Reddy <quic_varar@quicinc.com>,
<freedreno@lists.freedesktop.org>
Cc: <dri-devel@lists.freedesktop.org>, <quic_jesszhan@quicinc.com>,
<neil.armstrong@linaro.org>, <abel.vesa@linaro.org>,
<quic_khsieh@quicinc.com>, Rob Clark <robdclark@chromium.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/msm/dp: fix the max supported bpp logic
Date: Tue, 30 Jul 2024 10:58:11 -0700 [thread overview]
Message-ID: <cecfbed5-aec1-439b-a866-4eebcd3bd421@quicinc.com> (raw)
In-Reply-To: <CAE-0n537mpOMkVWrXGSpjU8cHZtUZXFfdG1YTfevu2SRo1hPTQ@mail.gmail.com>
On 7/29/2024 1:08 PM, Stephen Boyd wrote:
> Quoting Abhinav Kumar (2024-07-29 11:28:35)
>>
>> Thanks for the feedback.
>>
>> Your change looks valid. We can use this and drop the max_t usage.
>>
>> Let me push this with your Suggested-by credits.
>
> You can take my
>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
>
> and either squash it in or make a follow-up.
Done, I have squashed it into this.
I have also re-tested and since the logic is the same, I have retained
Dmitry's Tested-by
next prev parent reply other threads:[~2024-07-30 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 22:03 [PATCH] drm/msm/dp: fix the max supported bpp logic Abhinav Kumar
2024-07-27 0:24 ` Stephen Boyd
2024-07-29 18:28 ` Abhinav Kumar
2024-07-29 20:08 ` Stephen Boyd
2024-07-30 17:58 ` Abhinav Kumar [this message]
2024-07-27 12:51 ` Dmitry Baryshkov
2024-07-29 18:38 ` Abhinav Kumar
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=cecfbed5-aec1-439b-a866-4eebcd3bd421@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=groeck@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_varar@quicinc.com \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.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