From: "Grodzovsky, Andrey" <Andrey.Grodzovsky@amd.com>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
Nayan Deshmukh <nayan26deshmukh@gmail.com>,
Eric Anholt <eric@anholt.net>, Pixel Ding <Pixel.Ding@amd.com>,
Sharat Masetty <smasetty@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/sched: Fix description of drm_sched_stop
Date: Tue, 23 Apr 2019 14:17:47 +0000 [thread overview]
Message-ID: <8c7c1779-2617-58be-83c5-5145b0edd7fa@amd.com> (raw)
In-Reply-To: <20190420125053.32150-1-j.neuschaefer@gmx.net>
Reviewed-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
Andrey
On 4/20/19 8:50 AM, Jonathan Neuschäfer wrote:
> Since commit 222b5f044159 ("drm/sched: Refactor ring mirror list
> handling."), drm_sched_hw_job_reset is no longer there, so let's adjust
> the doc comment accordingly.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
> drivers/gpu/drm/scheduler/sched_main.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/scheduler/sched_main.c b/drivers/gpu/drm/scheduler/sched_main.c
> index 19fc601c9eeb..a1bec2779e76 100644
> --- a/drivers/gpu/drm/scheduler/sched_main.c
> +++ b/drivers/gpu/drm/scheduler/sched_main.c
> @@ -366,10 +366,9 @@ void drm_sched_increase_karma(struct drm_sched_job *bad)
> EXPORT_SYMBOL(drm_sched_increase_karma);
>
> /**
> - * drm_sched_hw_job_reset - stop the scheduler if it contains the bad job
> + * drm_sched_stop - stop the scheduler
> *
> * @sched: scheduler instance
> - * @bad: bad scheduler job
> *
> */
> void drm_sched_stop(struct drm_gpu_scheduler *sched)
> --
> 2.20.1
>
prev parent reply other threads:[~2019-04-23 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 12:50 Jonathan Neuschäfer
2019-04-23 14:17 ` Grodzovsky, Andrey [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=8c7c1779-2617-58be-83c5-5145b0edd7fa@amd.com \
--to=andrey.grodzovsky@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Pixel.Ding@amd.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=j.neuschaefer@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nayan26deshmukh@gmail.com \
--cc=smasetty@codeaurora.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®