From: "Christian König" <christian.koenig@amd.com>
To: Luben Tuikov <luben.tuikov@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] drm/sched: Add description of parameters in job_done
Date: Tue, 17 Oct 2023 19:12:00 +0200 [thread overview]
Message-ID: <04ce32e6-4000-404b-8f9b-7c6e5ee5d433@amd.com> (raw)
In-Reply-To: <20231017151521.12388-1-luben.tuikov@amd.com>
Am 17.10.23 um 17:15 schrieb Luben Tuikov:
> Fix a kernel test robot complaint that there's no description of the "result"
> parameter to drm_sched_job_done() function.
>
> Cc: Christian König <christian.koenig@amd.com>
> Fixes: 539f9ee4b52a8b ("drm/scheduler: properly forward fence errors")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202310172018.eaPyawVC-lkp@intel.com/
> Signed-off-by: Luben Tuikov <luben.tuikov@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/scheduler/sched_main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/scheduler/sched_main.c b/drivers/gpu/drm/scheduler/sched_main.c
> index 5a3a622fc672f3..6f2cf72e79b15e 100644
> --- a/drivers/gpu/drm/scheduler/sched_main.c
> +++ b/drivers/gpu/drm/scheduler/sched_main.c
> @@ -259,6 +259,7 @@ drm_sched_rq_select_entity_fifo(struct drm_sched_rq *rq)
> /**
> * drm_sched_job_done - complete a job
> * @s_job: pointer to the job which is done
> + * @result: The result of the finished scheduler fence.
> *
> * Finish the job's fence and wake up the worker thread.
> */
>
> base-commit: 213f891525c222e8ed145ce1ce7ae1f47921cb9c
prev parent reply other threads:[~2023-10-17 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 15:15 Luben Tuikov
2023-10-17 17:12 ` 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=04ce32e6-4000-404b-8f9b-7c6e5ee5d433@amd.com \
--to=christian.koenig@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luben.tuikov@amd.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
all inboxes | Powered by JetHome®