From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>, <robdclark@gmail.com>,
<sean@poorly.run>, <swboyd@chromium.org>, <dianders@chromium.org>,
<vkoul@kernel.org>, <daniel@ffwll.ch>, <airlied@gmail.com>,
<agross@kernel.org>, <dmitry.baryshkov@linaro.org>,
<andersson@kernel.org>
Cc: <quic_sbillaka@quicinc.com>, <freedreno@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/msm/dpu: add DSC range checking during resource reservation
Date: Tue, 11 Apr 2023 14:36:09 -0700 [thread overview]
Message-ID: <a8deba9a-0be1-b70b-8a6d-4a35d5788b2f@quicinc.com> (raw)
In-Reply-To: <1681247380-1607-1-git-send-email-quic_khsieh@quicinc.com>
On 4/11/2023 2:09 PM, Kuogee Hsieh wrote:
> Perform DSC range checking to make sure correct DSC is requested before
> reserve resource for it.
>
> Fixes: c985d7bb64ff ("drm/msm/disp/dpu1: Add DSC support in RM")
I cannot find any fixes tag with this hash.
This is the right one.
Fixes: f2803ee91a41 ("drm/msm/disp/dpu1: Add DSC support in RM")
> Signed-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
> ---
Otherwise, seems quite reasonable to me,
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
next prev parent reply other threads:[~2023-04-11 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 21:09 Kuogee Hsieh
2023-04-11 21:36 ` Abhinav Kumar [this message]
2023-04-11 22:22 ` Dmitry Baryshkov
2023-04-11 22:24 ` Marijn Suijten
2023-04-11 22:32 ` [Freedreno] " Abhinav Kumar
2023-04-12 1:06 ` Dmitry Baryshkov
2023-04-12 1:50 ` Abhinav Kumar
2023-04-12 7:38 ` Marijn Suijten
2023-04-12 17:48 ` Abhinav Kumar
2023-04-12 18:50 ` Marijn Suijten
2023-04-12 18:56 ` Dmitry Baryshkov
2023-04-12 18:59 ` 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=a8deba9a-0be1-b70b-8a6d-4a35d5788b2f@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®