From: "Christian König" <christian.koenig@amd.com>
To: Luben Tuikov <ltuikov89@gmail.com>,
Direct Rendering Infrastructure - Development
<dri-devel@lists.freedesktop.org>
Cc: Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Danilo Krummrich <dakr@redhat.com>,
Alex Deucher <alexander.deucher@amd.com>,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/sched: Rename priority MIN to LOW
Date: Mon, 27 Nov 2023 15:20:16 +0100 [thread overview]
Message-ID: <7429262c-6dea-4dcc-bf7e-54d2277dabf1@amd.com> (raw)
In-Reply-To: <49388112-f42a-448c-9f68-e41266c4408c@gmail.com>
Am 27.11.23 um 15:13 schrieb Luben Tuikov:
> On 2023-11-27 08:55, Christian König wrote:
>> Hi Luben,
>>
>> Am 24.11.23 um 08:57 schrieb Christian König:
>>> Am 24.11.23 um 06:27 schrieb Luben Tuikov:
>>>> Rename DRM_SCHED_PRIORITY_MIN to DRM_SCHED_PRIORITY_LOW.
>>>>
>>>> This mirrors DRM_SCHED_PRIORITY_HIGH, for a list of DRM scheduler
>>>> priorities
>>>> in ascending order,
>>>> DRM_SCHED_PRIORITY_LOW,
>>>> DRM_SCHED_PRIORITY_NORMAL,
>>>> DRM_SCHED_PRIORITY_HIGH,
>>>> DRM_SCHED_PRIORITY_KERNEL.
>>>>
>>>> Cc: Rob Clark <robdclark@gmail.com>
>>>> Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
>>>> Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>> Cc: Danilo Krummrich <dakr@redhat.com>
>>>> Cc: Alex Deucher <alexander.deucher@amd.com>
>>>> Cc: Christian König <christian.koenig@amd.com>
>>>> Cc: linux-arm-msm@vger.kernel.org
>>>> Cc: freedreno@lists.freedesktop.org
>>>> Cc: dri-devel@lists.freedesktop.org
>>>> Signed-off-by: Luben Tuikov <ltuikov89@gmail.com>
>>> Reviewed-by: Christian König <christian.koenig@amd.com>
>> Looks like you missed one usage in Nouveau:
>>
>> drivers/gpu/drm/nouveau/nouveau_sched.c:21:41: error:
>> ‘DRM_SCHED_PRIORITY_MIN’ undeclared here (not in a function); did you
>> mean ‘DRM_SCHED_PRIORITY_LOW’?
>> 21 | NOUVEAU_SCHED_PRIORITY_SINGLE = DRM_SCHED_PRIORITY_MIN,
>> | ^~~~~~~~~~~~~~~~~~~~~~
>> | DRM_SCHED_PRIORITY_LOW
>>
>> This now results in a build error on drm-misc-next.
> I'm waiting for someone to R-B the fix I posted two days ago:
> https://lore.kernel.org/r/20231125192246.87268-2-ltuikov89@gmail.com
There must be something wrong with the dri-devel mailing list (or my
gmail, but I doubt so). I don't see this mail in my inbox anywhere.
Feel free to add my rb and push it.
Thanks,
Christian.
next prev parent reply other threads:[~2023-11-27 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 5:27 [PATCH 0/2] Make scheduling of the same index, the same Luben Tuikov
2023-11-24 5:27 ` [PATCH 1/2] drm/sched: Rename priority MIN to LOW Luben Tuikov
2023-11-24 7:57 ` Christian König
2023-11-27 13:55 ` Christian König
2023-11-27 14:13 ` Luben Tuikov
2023-11-27 14:20 ` Christian König [this message]
2023-11-27 14:35 ` Luben Tuikov
2023-11-24 5:27 ` [PATCH 2/2] drm/sched: Reverse run-queue priority enumeration Luben Tuikov
2023-11-24 8:04 ` Christian König
2023-11-24 8:22 ` Luben Tuikov
2023-11-24 9:38 ` Christian König
2023-11-25 4:22 ` Luben Tuikov
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=7429262c-6dea-4dcc-bf7e-54d2277dabf1@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=dakr@redhat.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=ltuikov89@gmail.com \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.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