From: Daniel Vetter <daniel@ffwll.ch>
To: "Grodzovsky, Andrey" <Andrey.Grodzovsky@amd.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/sched: Fix make htmldocs warnings.
Date: Wed, 29 May 2019 21:36:15 +0200 [thread overview]
Message-ID: <20190529193615.GX21222@phenom.ffwll.local> (raw)
In-Reply-To: <aafdf860-4f83-1830-cbf4-855f97a56fb0@amd.com>
On Wed, May 29, 2019 at 04:43:45PM +0000, Grodzovsky, Andrey wrote:
> I don't, sorry.
Should we fix that? Seems like you do plenty of scheduler stuff, so would
make sense I guess ...
-Daniel
>
> Andrey
>
> On 5/29/19 12:42 PM, Alex Deucher wrote:
> > On Wed, May 29, 2019 at 10:29 AM Andrey Grodzovsky
> > <andrey.grodzovsky@amd.com> wrote:
> >> Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
> > Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> >
> > I'll push it to drm-misc in a minute unless you have commit rights.
> >
> > Alex
> >
> >> ---
> >> drivers/gpu/drm/scheduler/sched_main.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/drivers/gpu/drm/scheduler/sched_main.c b/drivers/gpu/drm/scheduler/sched_main.c
> >> index 49e7d07..c1058ee 100644
> >> --- a/drivers/gpu/drm/scheduler/sched_main.c
> >> +++ b/drivers/gpu/drm/scheduler/sched_main.c
> >> @@ -353,6 +353,7 @@ EXPORT_SYMBOL(drm_sched_increase_karma);
> >> * drm_sched_stop - stop the scheduler
> >> *
> >> * @sched: scheduler instance
> >> + * @bad: job which caused the time out
> >> *
> >> * Stop the scheduler and also removes and frees all completed jobs.
> >> * Note: bad job will not be freed as it might be used later and so it's
> >> @@ -422,6 +423,7 @@ EXPORT_SYMBOL(drm_sched_stop);
> >> * drm_sched_job_recovery - recover jobs after a reset
> >> *
> >> * @sched: scheduler instance
> >> + * @full_recovery: proceed with complete sched restart
> >> *
> >> */
> >> void drm_sched_start(struct drm_gpu_scheduler *sched, bool full_recovery)
> >> --
> >> 2.7.4
> >>
> >> _______________________________________________
> >> dri-devel mailing list
> >> dri-devel@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-29 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 14:29 [PATCH] drm/sched: Fix make htmldocs warnings Andrey Grodzovsky
[not found] ` <1559140180-6762-1-git-send-email-andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>
2019-05-29 16:42 ` Alex Deucher
2019-05-29 16:43 ` Grodzovsky, Andrey
2019-05-29 19:36 ` Daniel Vetter [this message]
2019-05-30 15:04 ` Christian König
[not found] ` <bc79d169-0768-9671-660f-ffe4ceee4b47-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-06-03 7:24 ` Daniel Vetter
[not found] ` <20190603072434.GZ21222-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-06-03 14:36 ` Grodzovsky, Andrey
2019-05-29 19:34 ` Daniel Vetter
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=20190529193615.GX21222@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Andrey.Grodzovsky@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.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