dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 4/6] drm/gpu.tmpl: Don't forget to rename the include directives, too
Date: Thu, 02 Jun 2016 16:52:08 +0300	[thread overview]
Message-ID: <87eg8f8zqv.fsf@intel.com> (raw)
In-Reply-To: <1464729075-22243-4-git-send-email-daniel.vetter@ffwll.ch>

On Wed, 01 Jun 2016, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> We need to get folks to run
>
> $ make htmldocs
>
> more often and actually check the output. With the fancy new sphinx
> stuff there's hopefully no more excuses.

I think we should make kernel-doc return non-zero exit code if you
specify a function or doc section with -function and it's not
found. This should be a build stopping error, not a warning.

BR,
Jani.



>
> Fixes: 286dbb8d5d80 ("drm/atomic: Rename async parameter to nonblocking.")
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
>  Documentation/DocBook/gpu.tmpl | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/DocBook/gpu.tmpl b/Documentation/DocBook/gpu.tmpl
> index cb130514cedf..053cc1f46af9 100644
> --- a/Documentation/DocBook/gpu.tmpl
> +++ b/Documentation/DocBook/gpu.tmpl
> @@ -1570,7 +1570,7 @@ void intel_crt_init(struct drm_device *dev)
>        </sect3>
>        <sect3>
>  	<title>Implementing Asynchronous Atomic Commit</title>
> -!Pdrivers/gpu/drm/drm_atomic_helper.c implementing async commit
> +!Pdrivers/gpu/drm/drm_atomic_helper.c implementing nonblocking commit
>        </sect3>
>        <sect3>
>  	<title>Atomic State Reset and Initialization</title>

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-06-02 13:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 21:11 [PATCH 1/6] drm/doc: Update kerneldoc for drm_crtc.h Daniel Vetter
2016-05-31 21:11 ` [PATCH 2/6] drm/atomic-helper: Fixup kerneldoc for drm_atomic_helper_legacy_gamma_set Daniel Vetter
2016-05-31 21:11 ` [PATCH 3/6] drm/doc: Improve kernel-doc for drm_fb_cma_helper.c Daniel Vetter
2016-06-02 14:31   ` Liviu Dudau
2016-06-02 22:15   ` Laurent Pinchart
2016-05-31 21:11 ` [PATCH 4/6] drm/gpu.tmpl: Don't forget to rename the include directives, too Daniel Vetter
2016-06-02 13:52   ` Jani Nikula [this message]
2016-06-02 14:28     ` Daniel Vetter
2016-05-31 21:11 ` [PATCH 5/6] drm/doc: Drop kerneldoc for static functions in drm_irq.c Daniel Vetter
2016-05-31 21:11 ` [PATCH 6/6] drm/doc: Switch to sphinx/rst fixed-width quoting Daniel Vetter
2016-06-01  8:46   ` [PATCH] " Daniel Vetter
2016-06-01  9:46     ` Jani Nikula
2016-06-01 13:33       ` Daniel Vetter
2016-06-01 13:46         ` Jani Nikula
2016-06-01 14:44           ` Daniel Vetter
2016-06-02 14:29     ` Daniel Vetter
2016-06-02 13:50 ` [PATCH 1/6] drm/doc: Update kerneldoc for drm_crtc.h Jani Nikula
2016-06-02 14:28 ` Liviu Dudau

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=87eg8f8zqv.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --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