dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Marek Vasut <marex@denx.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
	dri-devel@lists.freedesktop.org,
	Lucas Stach <l.stach@pengutronix.de>
Subject: [drm-intel:topic/drm-misc 23/26] include/drm/drm_fb_cma_helper.h:45:13: warning: 'struct drm_plane_state' declared inside parameter list will not be visible outside of this definition or declaration
Date: Tue, 15 Nov 2016 16:29:04 +0800	[thread overview]
Message-ID: <201611151602.dMzDYKIm%fengguang.wu@intel.com> (raw)

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

tree:   git://anongit.freedesktop.org/drm-intel topic/drm-misc
head:   35cf03508d8466ecc5199c9d609e74e85bec785b
commit: 14d7f96f90fb65c2ca0e0ac7df237e06ff001c29 [23/26] drm/fb_cma_helper: Add drm_fb_cma_prepare_fb() helper
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        git checkout 14d7f96f90fb65c2ca0e0ac7df237e06ff001c29
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   In file included from drivers/gpu/drm/vc4/vc4_drv.c:18:0:
>> include/drm/drm_fb_cma_helper.h:45:13: warning: 'struct drm_plane_state' declared inside parameter list will not be visible outside of this definition or declaration
         struct drm_plane_state *state);
                ^~~~~~~~~~~~~~~
>> include/drm/drm_fb_cma_helper.h:44:34: warning: 'struct drm_plane' declared inside parameter list will not be visible outside of this definition or declaration
    int drm_fb_cma_prepare_fb(struct drm_plane *plane,
                                     ^~~~~~~~~

vim +45 include/drm/drm_fb_cma_helper.h

    38	struct drm_framebuffer *drm_fb_cma_create(struct drm_device *dev,
    39		struct drm_file *file_priv, const struct drm_mode_fb_cmd2 *mode_cmd);
    40	
    41	struct drm_gem_cma_object *drm_fb_cma_get_gem_obj(struct drm_framebuffer *fb,
    42		unsigned int plane);
    43	
  > 44	int drm_fb_cma_prepare_fb(struct drm_plane *plane,
  > 45				  struct drm_plane_state *state);
    46	
    47	#ifdef CONFIG_DEBUG_FS
    48	struct seq_file;

---
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: 56846 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-11-15  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  8:29 kbuild test robot [this message]
2016-11-15  8:47 ` [drm-intel:topic/drm-misc 23/26] include/drm/drm_fb_cma_helper.h:45:13: warning: 'struct drm_plane_state' declared inside parameter list will not be visible outside of this definition or declaration Daniel Vetter
2016-11-15 10:02   ` Daniel Vetter
2016-11-15 10:53     ` Marek Vasut

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=201611151602.dMzDYKIm%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=l.stach@pengutronix.de \
    --cc=marex@denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).