From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Anholt <eric@anholt.net>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Sean Paul <seanpaul@chromium.org>, Qiang Yu <yuq825@gmail.com>,
Sean Paul <sean@poorly.run>
Subject: Re: [PATCH] drm/gem: Fix sphinx warnings
Date: Thu, 25 Apr 2019 08:35:01 +0200 [thread overview]
Message-ID: <20190425063501.GY9857@phenom.ffwll.local> (raw)
In-Reply-To: <871s1rkqu3.fsf@anholt.net>
On Wed, Apr 24, 2019 at 02:59:00PM -0700, Eric Anholt wrote:
> Sean Paul <sean@poorly.run> writes:
>
> > From: Sean Paul <seanpaul@chromium.org>
> >
> > Sphinx really wants colons after arguments :/
> >
> > Fixes the following warnings:
> > drm_gem.c:1384: warning: Function parameter or member 'fence_array' not described in 'drm_gem_fence_array_add'
> > drm_gem.c:1384: warning: Function parameter or member 'fence' not described in 'drm_gem_fence_array_add'
> > drm_gem.c:1435: warning: Function parameter or member 'fence_array' not described in 'drm_gem_fence_array_add_implicit'
> > drm_gem.c:1435: warning: Function parameter or member 'obj' not described in 'drm_gem_fence_array_add_implicit'
> > drm_gem.c:1435: warning: Function parameter or member 'write' not described in 'drm_gem_fence_array_add_implicit'
>
> Hopefully some day we can move to gitlab and have CI and make sure we
> don't screw this stuff up ever again.
0day is supposed to catch new htmldocs errors meanwhile, but I get a
feeling it's totally overloaded and so always a bit too late :-/ Or people
just ignore 0day mails, dunno ...
-Daniel
>
> Reviewed-by: Eric Anholt <eric@anholt.net>
--
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-04-25 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 20:49 [PATCH] drm/gem: Fix sphinx warnings Sean Paul
2019-04-24 21:59 ` Eric Anholt
2019-04-25 6:35 ` Daniel Vetter [this message]
2019-04-25 14:16 ` Sean Paul
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=20190425063501.GY9857@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=maxime.ripard@bootlin.com \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.org \
--cc=yuq825@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.