linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Eric Anholt <eric@anholt.net>
Cc: kbuild-all@01.org, dri-devel@lists.freedesktop.org,
	Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>,
	Haneen Mohammed <hamohammed.sa@gmail.com>,
	linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>
Subject: Re: [PATCH 2/2] drm/vkms: Add PRIME support by converting to Noralf's shmem helpers.
Date: Tue, 27 Nov 2018 08:48:27 +0800	[thread overview]
Message-ID: <201811270831.oqsdiNux%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181126215929.20546-2-eric@anholt.net>

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

Hi Eric,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v4.20-rc4 next-20181126]
[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/Eric-Anholt/drm-vkms-Drop-custom-vkms_dumb_map/20181127-072142
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/vkms/vkms_drv.c:22:10: fatal error: drm/drm_gem_shmem_helper.h: No such file or directory
    #include <drm/drm_gem_shmem_helper.h>
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
>> drivers/gpu/drm/vkms/vkms_plane.c:14:10: fatal error: drm/drm_gem_shmem_helper.h: No such file or directory
    #include <drm/drm_gem_shmem_helper.h>
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
>> drivers/gpu/drm/vkms/vkms_gem.c:10:10: fatal error: drm/drm_gem_shmem_helper.h: No such file or directory
    #include <drm/drm_gem_shmem_helper.h>
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
>> drivers/gpu/drm/vkms/vkms_crc.c:7:10: fatal error: drm/drm_gem_shmem_helper.h: No such file or directory
    #include <drm/drm_gem_shmem_helper.h>
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.

vim +22 drivers/gpu/drm/vkms/vkms_drv.c

  > 22	#include <drm/drm_gem_shmem_helper.h>
    23	#include <drm/drm_fb_helper.h>
    24	#include "vkms_drv.h"
    25	

---
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: 66023 bytes --]

  reply	other threads:[~2018-11-27  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 21:59 [PATCH 1/2] drm/vkms: Drop custom vkms_dumb_map() Eric Anholt
2018-11-26 21:59 ` [PATCH 2/2] drm/vkms: Add PRIME support by converting to Noralf's shmem helpers Eric Anholt
2018-11-27  0:48   ` kbuild test robot [this message]
2018-11-27  9:11   ` Daniel Vetter
2018-11-27 20:38 [PATCH 1/2] drm: Add library for shmem backed GEM objects Eric Anholt
2018-11-27 20:38 ` [PATCH 2/2] drm/vkms: Add PRIME support by converting to Noralf's shmem helpers Eric Anholt

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=201811270831.oqsdiNux%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=hamohammed.sa@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigosiqueiramelo@gmail.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 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).