public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
	CQ Tang <cq.tang@intel.com>
Subject: Re: [PATCH v5 2/2] drm/i915: add in-kernel blitter client
Date: Wed, 29 May 2019 17:26:44 +0800	[thread overview]
Message-ID: <201905291715.bo8P9JCV%lkp@intel.com> (raw)
In-Reply-To: <20190528195724.2786-2-matthew.auld@intel.com>

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

Hi Matthew,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on drm-intel/for-linux-next]
[cannot apply to v5.2-rc2 next-20190528]
[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/Matthew-Auld/drm-i915-gtt-grab-wakeref-in-gen6_alloc_va_range/20190529-132242
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-n018201921 (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 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/i915/gem/i915_gem_client_blt.c:305:0:
>> drivers/gpu/drm/i915/gem/selftests/i915_gem_client_blt.c:6:10: fatal error: ../i915_selftest.h: No such file or directory
    #include "../i915_selftest.h"
             ^~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
   In file included from drivers/gpu/drm/i915/gem/i915_gem_object_blt.c:108:0:
>> drivers/gpu/drm/i915/gem/selftests/i915_gem_object_blt.c:6:10: fatal error: ../i915_selftest.h: No such file or directory
    #include "../i915_selftest.h"
             ^~~~~~~~~~~~~~~~~~~~
   compilation terminated.

vim +6 drivers/gpu/drm/i915/gem/selftests/i915_gem_client_blt.c

   > 6	#include "../i915_selftest.h"
     7	

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

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

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

  parent reply	other threads:[~2019-05-29  9:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 19:57 [PATCH v5 1/2] drm/i915/gtt: grab wakeref in gen6_alloc_va_range Matthew Auld
2019-05-28 19:57 ` [PATCH v5 2/2] drm/i915: add in-kernel blitter client Matthew Auld
2019-05-28 20:45   ` Changqing Tang
2019-05-28 20:52   ` Chris Wilson
2019-05-28 22:32     ` Chris Wilson
2019-05-29  9:26   ` kbuild test robot [this message]
2019-05-28 20:44 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/2] drm/i915/gtt: grab wakeref in gen6_alloc_va_range Patchwork
2019-05-28 20:46 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-05-28 21:00 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-29  8:01 ` ✓ Fi.CI.IGT: " Patchwork

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=201905291715.bo8P9JCV%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cq.tang@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=matthew.auld@intel.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