dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: nouveau@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org,
	Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
	kbuild-all@01.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
	Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH v2 1/2] drm: Wrap the check for atomic_commit implementation
Date: Thu, 22 Dec 2016 16:07:58 +0800	[thread overview]
Message-ID: <201612221631.b5ydxtgn%fengguang.wu@intel.com> (raw)
In-Reply-To: <1482351129-10398-1-git-send-email-dhinakaran.pandiyan@intel.com>

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

Hi Dhinakaran,

[auto build test ERROR on drm/drm-next]
[also build test ERROR on next-20161222]
[cannot apply to v4.9]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Dhinakaran-Pandiyan/drm-Wrap-the-check-for-atomic_commit-implementation/20161222-153523
base:   git://people.freedesktop.org/~airlied/linux.git drm-next
config: i386-randconfig-s1-201651 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c:19:0:
   include/drm/drm_atomic.h: In function 'drm_drv_uses_atomic_modeset':
>> include/drm/drm_atomic.h:436:12: error: dereferencing pointer to incomplete type 'struct drm_device'
     return dev->mode_config.funcs->atomic_commit ? true : false;
               ^~

vim +436 include/drm/drm_atomic.h

   430	 *
   431	 * This check is useful if drivers do not have DRIVER_ATOMIC set but
   432	 * have atomic modesetting internally implemented.
   433	 */
   434	static inline bool drm_drv_uses_atomic_modeset(struct drm_device *dev)
   435	{
 > 436		return dev->mode_config.funcs->atomic_commit ? true : false;
   437	}
   438	
   439	#endif /* DRM_ATOMIC_H_ */

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

  parent reply	other threads:[~2016-12-22  8:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  1:03 [PATCH 1/2] drm: Wrap the check for atomic_commit implementation Dhinakaran Pandiyan
2016-12-21  1:03 ` [PATCH 2/2] drm: Get atomic property value even if DRIVER_ATOMIC is not set Dhinakaran Pandiyan
2016-12-21  8:53   ` Daniel Vetter
2016-12-21  8:51 ` [PATCH 1/2] drm: Wrap the check for atomic_commit implementation Daniel Vetter
2016-12-21 20:12   ` [PATCH v2 " Dhinakaran Pandiyan
2016-12-21 20:12     ` [PATCH v2 2/2] drm: Get atomic property value even if DRIVER_ATOMIC is not set Dhinakaran Pandiyan
2017-01-03 16:06       ` Alex Deucher
2016-12-22  7:11     ` [PATCH v2 1/2] drm: Wrap the check for atomic_commit implementation Daniel Vetter
2016-12-22  8:07     ` kbuild test robot [this message]
2016-12-22  8:36     ` [Intel-gfx] " Ander Conselvan De Oliveira
     [not found]       ` <1482395761.4759.32.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-22  8:52         ` Daniel Vetter
2016-12-22  9:14           ` Pandiyan, Dhinakaran
2016-12-21  9:23 ` [PATCH " Ville Syrjälä

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=201612221631.b5ydxtgn%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bskeggs@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=nouveau@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