All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 01/11] drm/drm-kms.rst: Remove unused drm_fourcc.h include directive
Date: Tue, 19 Jul 2016 10:34:13 +0200	[thread overview]
Message-ID: <20160719083413.GN17101@phenom.ffwll.local> (raw)
In-Reply-To: <1468612088-9721-1-git-send-email-daniel.vetter@ffwll.ch>

On Fri, Jul 15, 2016 at 09:47:58PM +0200, Daniel Vetter wrote:
> Right now there's nothing, and kernel-doc produces a warning because
> of that. Remove it until we need it for a clean build.
> 
> Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>

Pulled in the entire pile with Chris' irc-ack, and the few things he
commented on polished.
-Daniel

> ---
>  Documentation/gpu/drm-kms.rst | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/Documentation/gpu/drm-kms.rst b/Documentation/gpu/drm-kms.rst
> index 0e1c80436c1d..675221f0a64b 100644
> --- a/Documentation/gpu/drm-kms.rst
> +++ b/Documentation/gpu/drm-kms.rst
> @@ -67,9 +67,6 @@ drivers can manually clean up a framebuffer at module unload time with
>  DRM Format Handling
>  -------------------
>  
> -.. kernel-doc:: include/drm/drm_fourcc.h
> -   :internal:
> -
>  .. kernel-doc:: drivers/gpu/drm/drm_fourcc.c
>     :export:
>  
> -- 
> 2.8.1
> 

-- 
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

      parent reply	other threads:[~2016-07-19  8:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 19:47 [PATCH 01/11] drm/drm-kms.rst: Remove unused drm_fourcc.h include directive Daniel Vetter
2016-07-15 19:47 ` [PATCH 02/11] drm/doc: Add kerneldoc for @index Daniel Vetter
2016-07-15 20:06   ` Chris Wilson
2016-07-18  7:15     ` Daniel Vetter
2016-07-18  7:29       ` Chris Wilson
2016-07-15 19:48 ` [PATCH 03/11] drm/doc: document all the properties in drm_mode_config Daniel Vetter
2016-07-15 19:48 ` [PATCH 04/11] drm: Extract&Document drm_irq.h Daniel Vetter
2016-07-15 19:48 ` [PATCH 05/11] drm/doc: Fix missing kerneldoc for drm_dp_helper.c Daniel Vetter
2016-07-15 19:48 ` [PATCH 06/11] drm/dp-mst: Remove tx_down_in_progress Daniel Vetter
2016-07-15 19:58   ` Chris Wilson
2016-07-15 19:48 ` [PATCH 07/11] drm/dp-mst: Missing kernel doc Daniel Vetter
2016-07-15 19:48 ` [PATCH 08/11] drm/i915: Fixup kerneldoc code snippets in intel_uncore.c Daniel Vetter
2016-07-15 19:48 ` [PATCH 09/11] drm/i915: Clean up kerneldoc for intel_lrc.c Daniel Vetter
2016-07-15 20:01   ` [Intel-gfx] " Chris Wilson
2016-07-15 19:48 ` [PATCH 10/11] drm/i915: Update missing kerneldoc Daniel Vetter
2016-07-15 19:48 ` [PATCH 11/11] drm/doc: Spinx leftovers Daniel Vetter
2016-07-19  8:34 ` Daniel Vetter [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=20160719083413.GN17101@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=laurent.pinchart+renesas@ideasonboard.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.