From: "Christian König" <christian.koenig@amd.com>
To: Nayan Deshmukh <nayan26deshmukh@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: alexander.deucher@amd.com
Subject: Re: [PATCH] drm/v3d: fix build error due to change in scheduler struct
Date: Thu, 27 Sep 2018 14:26:47 +0200 [thread overview]
Message-ID: <e701fdd0-427d-5229-f14b-eaeb741c0ffb@amd.com> (raw)
In-Reply-To: <20180927103056.2159-1-nayan26deshmukh@gmail.com>
Am 27.09.2018 um 12:30 schrieb Nayan Deshmukh:
> The work_tdr field was moved from drm_sched_job to drm_gpu_scheduler
> as part of a previous patch.
>
> Fixes: 4f07d88d8534 drm/scheduler: remove timeout work_struct from
> drm_sched_job
>
> Signed-off-by: Nayan Deshmukh <nayan26deshmukh@gmail.com>
I've squashed the two fixed together and pushed the result.
With a bit of luck Alex will squash them into the original patch before
pushing it upstream.
Christian.
> ---
> drivers/gpu/drm/v3d/v3d_sched.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/v3d/v3d_sched.c b/drivers/gpu/drm/v3d/v3d_sched.c
> index a5501581d96b..9243dea6e6ad 100644
> --- a/drivers/gpu/drm/v3d/v3d_sched.c
> +++ b/drivers/gpu/drm/v3d/v3d_sched.c
> @@ -168,7 +168,7 @@ v3d_job_timedout(struct drm_sched_job *sched_job)
> job->timedout_ctca = ctca;
> job->timedout_ctra = ctra;
>
> - schedule_delayed_work(&job->base.work_tdr,
> + schedule_delayed_work(&job->base.sched->work_tdr,
> job->base.sched->timeout);
> return;
> }
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-09-27 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 10:30 [PATCH] drm/v3d: fix build error due to change in scheduler struct Nayan Deshmukh
2018-09-27 12:26 ` Christian König [this message]
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=e701fdd0-427d-5229-f14b-eaeb741c0ffb@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=nayan26deshmukh@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