mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: kbuild-all@01.org, Daniel Vetter <daniel.vetter@intel.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	DRI devel <dri-devel@lists.freedesktop.org>,
	Mihail Atanassov <mihail.atanassov@arm.com>
Subject: Re: [PATCH v5 3/3] drm: mali-dp: Add writeback connector
Date: Sun, 28 May 2017 10:23:43 +0800	[thread overview]
Message-ID: <201705281056.Y13BjLKc%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170515172402.30452-4-Liviu.Dudau@arm.com>

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

Hi Brian,

[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.12-rc2 next-20170526]
[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/Liviu-Dudau/drm-mali-dp-Add-support-for-writeback-on-DP550-DP650/20170516-013246
base:   git://people.freedesktop.org/~airlied/linux.git drm-next
config: arm-allyesconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=arm 

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/arm/malidp_drv.c:31:0:
>> drivers/gpu/drm/arm/malidp_drv.h:16:31: fatal error: drm/drm_writeback.h: No such file or directory
    #include <drm/drm_writeback.h>
                                  ^
   compilation terminated.
--
>> drivers/gpu/drm/arm/malidp_mw.c:19:31: fatal error: drm/drm_writeback.h: No such file or directory
    #include <drm/drm_writeback.h>
                                  ^
   compilation terminated.

vim +16 drivers/gpu/drm/arm/malidp_drv.h

    10	 * ARM Mali DP500/DP550/DP650 KMS/DRM driver structures
    11	 */
    12	
    13	#ifndef __MALIDP_DRV_H__
    14	#define __MALIDP_DRV_H__
    15	
  > 16	#include <drm/drm_writeback.h>
    17	#include <drm/drm_encoder.h>
    18	#include <linux/mutex.h>
    19	#include <linux/wait.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: 61645 bytes --]

  reply	other threads:[~2017-05-28  2:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 17:23 [PATCH v5 0/3] drm/mali-dp: Add support for memory writeback engine Liviu Dudau
2017-05-15 17:24 ` [PATCH v5 1/3] drm: mali-dp: Add support for writeback on DP550/DP650 Liviu Dudau
2017-05-15 17:24 ` [PATCH v5 2/3] drm: mali-dp: Add RGB writeback formats for DP550/DP650 Liviu Dudau
2017-05-15 17:24 ` [PATCH v5 3/3] drm: mali-dp: Add writeback connector Liviu Dudau
2017-05-28  2:23   ` kbuild test robot [this message]
2017-06-02  8:34 ` [PATCH v5 0/3] drm/mali-dp: Add support for memory writeback engine Boris Brezillon
2017-06-02  9:24   ` Liviu Dudau

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=201705281056.Y13BjLKc%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihail.atanassov@arm.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

all inboxes | Powered by JetHome®