dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Nayan Deshmukh <nayan26deshmukh@gmail.com>,
	dri-devel@lists.freedesktop.org
Cc: ckoenig.leichtzumerken@gmail.com
Subject: Re: [PATCH] drm/scheduler: remove incorrect param documentation
Date: Sun, 25 Mar 2018 13:14:08 +0200	[thread overview]
Message-ID: <03cc179a-1b4d-a932-b22a-149eb7d3f757@amd.com> (raw)
In-Reply-To: <20180325110928.24839-1-nayan26deshmukh@gmail.com>

Am 25.03.2018 um 13:09 schrieb Nayan Deshmukh:
> Signed-off-by: Nayan Deshmukh <nayan26deshmukh@gmail.com>
> ---
>   drivers/gpu/drm/scheduler/gpu_scheduler.c | 1 -
>   1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/scheduler/gpu_scheduler.c b/drivers/gpu/drm/scheduler/gpu_scheduler.c
> index 0d95888ccc3e..27fdda1264f7 100644
> --- a/drivers/gpu/drm/scheduler/gpu_scheduler.c
> +++ b/drivers/gpu/drm/scheduler/gpu_scheduler.c
> @@ -117,7 +117,6 @@ drm_sched_rq_select_entity(struct drm_sched_rq *rq)
>    * @sched	The pointer to the scheduler
>    * @entity	The pointer to a valid drm_sched_entity
>    * @rq		The run queue this entity belongs
> - * @kernel	If this is an entity for the kernel
>    * @jobs	The max number of jobs in the job queue

If I'm not completely mistaken the jobs parameter is unused and we also 
have a @guilty parameter as well.

The description for the @guilty should be something like "atomic_t set 
to 1 when a job on this queue is found to be guilty causing a timeout".

Regards,
Christian.

>    *
>    * return 0 if succeed. negative error code on failure

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-03-25 11:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-25 11:09 [PATCH] drm/scheduler: remove incorrect param documentation Nayan Deshmukh
2018-03-25 11:14 ` Christian König [this message]
2018-03-25 11:21   ` Nayan Deshmukh
2018-03-25 11:29     ` Christian König
2018-03-26 15:21       ` [PATCH] drm/scheduler: fix " Nayan Deshmukh
2018-03-26 16:57         ` Christian König
2018-03-26 17:16           ` Nayan Deshmukh
2018-03-27  8:17         ` Daniel Vetter
2018-03-27 17:29           ` Nayan Deshmukh
2018-03-29 15:26             ` Alex Deucher
2018-03-29 17:08               ` Nayan Deshmukh
2018-03-26 15:29       ` [PATCH] drm/scheduler: remove incorrect " Nayan Deshmukh
2018-03-26 16:59         ` Christian König
2018-03-26 17:04           ` Nayan Deshmukh

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=03cc179a-1b4d-a932-b22a-149eb7d3f757@amd.com \
    --to=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.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