From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix a buch of kerneldoc warnings
Date: Fri, 3 Jun 2016 14:04:10 +0100 [thread overview]
Message-ID: <5751804A.7000201@linux.intel.com> (raw)
In-Reply-To: <20160602202127.GR7231@phenom.ffwll.local>
On 02/06/16 21:21, Daniel Vetter wrote:
> On Thu, Jun 02, 2016 at 04:19:48PM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Just a bunch of stale kerneldocs generating warnings when
>> building the docs. Mostly function parameters so not very
>> useful but still.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Minor nit: Mostly we dont put a blank line between the title - purpose
> line and the start of the @parameter list. There's also a bunch of
> kerneldoc comments that don't even start with the function name. Do they
> work and show up correctly in the generated output?
>
> One more special case below
Okay respun, however I don't see that anything from i915_gem.c is
showing up in the generated index -
Documentation/output/html/genindex.html#I.
At least it is not throwing that many warnings during the build.
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-03 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 15:19 [PATCH] drm/i915: Fix a buch of kerneldoc warnings Tvrtko Ursulin
2016-06-02 20:21 ` Daniel Vetter
2016-06-03 13:02 ` [PATCH v2] " Tvrtko Ursulin
2016-06-03 13:13 ` Chris Wilson
2016-06-06 8:42 ` Jani Nikula
2016-06-03 13:04 ` Tvrtko Ursulin [this message]
2016-06-03 6:09 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-06-03 13:48 ` ✗ Ro.CI.BAT: warning for drm/i915: Fix a buch of kerneldoc warnings (rev2) Patchwork
2016-06-06 12:07 ` Tvrtko Ursulin
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=5751804A.7000201@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
/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.