dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Stefan Christ <contact@stefanchrist.eu>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
	kbuild-all@01.org, dri-devel@lists.freedesktop.org
Subject: [drm-intel:topic/drm-misc 3/3] htmldocs: include/drm/drm_fb_helper.h:222: warning: Cannot understand * @DRM_FB_HELPER_DEFAULT_OPS:
Date: Fri, 30 Sep 2016 23:18:37 +0800	[thread overview]
Message-ID: <201609302329.OlfQQLZo%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

tree:   git://anongit.freedesktop.org/drm-intel topic/drm-misc
head:   6c4d6f9f997c5dafccb54b52167f0c4d0ea37874
commit: 6c4d6f9f997c5dafccb54b52167f0c4d0ea37874 [3/3] drm/fb-helper: add DRM_FB_HELPER_DEFAULT_OPS for fb_ops
reproduce: make htmldocs

All warnings (new ones prefixed by >>):

>> include/drm/drm_fb_helper.h:222: warning: Cannot understand  * @DRM_FB_HELPER_DEFAULT_OPS:
    on line 222 - I thought it was a doc line

vim +222 include/drm/drm_fb_helper.h

   206		 * Entry on the global kernel_fb_helper_list, used for kgdb entry/exit.
   207		 */
   208		struct list_head kernel_fb_list;
   209	
   210		/**
   211		 * @delayed_hotplug:
   212		 *
   213		 * A hotplug was received while fbdev wasn't in control of the DRM
   214		 * device, i.e. another KMS master was active. The output configuration
   215		 * needs to be reprobe when fbdev is in control again.
   216		 */
   217		bool delayed_hotplug;
   218	};
   219	
   220	/**
   221	 * @DRM_FB_HELPER_DEFAULT_OPS:
 > 222	 *
   223	 * Helper define to register default implementations of drm_fb_helper
   224	 * functions. To be used in struct fb_ops of drm drivers.
   225	 */
   226	#define DRM_FB_HELPER_DEFAULT_OPS \
   227		.fb_check_var	= drm_fb_helper_check_var, \
   228		.fb_set_par	= drm_fb_helper_set_par, \
   229		.fb_setcmap	= drm_fb_helper_setcmap, \
   230		.fb_blank	= drm_fb_helper_blank, \

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6406 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2016-09-30 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 15:18 kbuild test robot [this message]
2016-10-03  9:35 ` [drm-intel:topic/drm-misc 3/3] htmldocs: include/drm/drm_fb_helper.h:222: warning: Cannot understand * @DRM_FB_HELPER_DEFAULT_OPS: Jani Nikula
2016-10-03 13:50   ` [Intel-gfx] " Daniel Vetter
2016-10-04 21:36     ` [PATCH v2] drm/fb-helper: add DRM_FB_HELPER_DEFAULT_OPS for fb_ops Stefan Christ
2016-10-05  9:00       ` Gustavo Padovan
2016-10-05 13:13         ` Daniel Vetter
2016-10-05 18:34           ` [PATCH] drm/fb-helper: fix sphinx markup for DRM_FB_HELPER_DEFAULT_OPS Stefan Christ
2016-10-06  9:18             ` 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=201609302329.OlfQQLZo%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=contact@stefanchrist.eu \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.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