public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Arunpravin <Arunpravin.PaneerSelvam@amd.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	amd-gfx@lists.freedesktop.org
Cc: kbuild-all@lists.01.org,
	Arunpravin <Arunpravin.PaneerSelvam@amd.com>,
	matthew.auld@intel.com, tzimmermann@suse.de,
	alexander.deucher@amd.com, christian.koenig@amd.com
Subject: Re: [Intel-gfx] [PATCH v3 1/6] drm: move the buddy allocator from i915 into common drm
Date: Thu, 18 Nov 2021 04:45:47 +0800	[thread overview]
Message-ID: <202111180415.YMBr4Vac-lkp@intel.com> (raw)
In-Reply-To: <20211116201807.147486-1-Arunpravin.PaneerSelvam@amd.com>

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

Hi Arunpravin,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-intel/for-linux-next v5.16-rc1]
[cannot apply to drm-tip/drm-tip next-20211117]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Arunpravin/drm-move-the-buddy-allocator-from-i915-into-common-drm/20211117-041920
base:   git://anongit.freedesktop.org/drm/drm drm-next
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/47fb1aeae75661971f4526efddf4ae5b5738977f
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Arunpravin/drm-move-the-buddy-allocator-from-i915-into-common-drm/20211117-041920
        git checkout 47fb1aeae75661971f4526efddf4ae5b5738977f
        # save the attached .config to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

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

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/i915/intel_memory_region.c:242:
>> drivers/gpu/drm/i915/selftests/intel_memory_region.c:23:10: fatal error: i915_buddy.h: No such file or directory
      23 | #include "i915_buddy.h"
         |          ^~~~~~~~~~~~~~
   compilation terminated.


vim +23 drivers/gpu/drm/i915/selftests/intel_memory_region.c

232a6ebae419193 Matthew Auld     2019-10-08  14  
340be48f2c5a3c0 Matthew Auld     2019-10-25  15  #include "gem/i915_gem_context.h"
b908be543e44414 Matthew Auld     2019-10-25  16  #include "gem/i915_gem_lmem.h"
232a6ebae419193 Matthew Auld     2019-10-08  17  #include "gem/i915_gem_region.h"
340be48f2c5a3c0 Matthew Auld     2019-10-25  18  #include "gem/selftests/igt_gem_utils.h"
232a6ebae419193 Matthew Auld     2019-10-08  19  #include "gem/selftests/mock_context.h"
99919be74aa3753 Thomas Hellström 2021-06-17  20  #include "gt/intel_engine_pm.h"
6804da20bb549e3 Chris Wilson     2019-10-27  21  #include "gt/intel_engine_user.h"
b908be543e44414 Matthew Auld     2019-10-25  22  #include "gt/intel_gt.h"
d53ec322dc7de32 Matthew Auld     2021-06-16 @23  #include "i915_buddy.h"
99919be74aa3753 Thomas Hellström 2021-06-17  24  #include "gt/intel_migrate.h"
ba12993c5228015 Matthew Auld     2020-01-29  25  #include "i915_memcpy.h"
d53ec322dc7de32 Matthew Auld     2021-06-16  26  #include "i915_ttm_buddy_manager.h"
01377a0d7e6648b Abdiel Janulgue  2019-10-25  27  #include "selftests/igt_flush_test.h"
2f0b97ca0211863 Matthew Auld     2019-10-08  28  #include "selftests/i915_random.h"
232a6ebae419193 Matthew Auld     2019-10-08  29  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66043 bytes --]

      parent reply	other threads:[~2021-11-17 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 20:18 [Intel-gfx] [PATCH v3 1/6] drm: move the buddy allocator from i915 into common drm Arunpravin
2021-11-16 20:18 ` [Intel-gfx] [PATCH v3 2/6] drm: improve drm_buddy_alloc function Arunpravin
2021-11-17 18:39   ` Matthew Auld
2021-11-23 22:39     ` Arunpravin
2021-11-24 10:33       ` Matthew Auld
2021-11-16 20:18 ` [Intel-gfx] [PATCH v3 3/6] drm: implement top-down allocation method Arunpravin
2021-11-16 20:18 ` [Intel-gfx] [PATCH v3 4/6] drm: implement a method to free unused pages Arunpravin
2021-11-17 19:02   ` Matthew Auld
2021-11-23 22:40     ` Arunpravin
2021-11-16 20:18 ` [Intel-gfx] [PATCH v3 5/6] drm/amdgpu: move vram inline functions into a header Arunpravin
2021-11-16 20:18 ` [Intel-gfx] [PATCH v3 6/6] drm/amdgpu: add drm buddy support to amdgpu Arunpravin
2021-11-17  2:55 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v3,1/6] drm: move the buddy allocator from i915 into common drm Patchwork
2021-11-17  8:03 ` [Intel-gfx] [PATCH v3 1/6] " Christian König
2021-11-17 17:05   ` Arunpravin
2021-11-17 17:52 ` Matthew Auld
2021-11-17 20:45 ` kernel test robot [this message]

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=202111180415.YMBr4Vac-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Arunpravin.PaneerSelvam@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=matthew.auld@intel.com \
    --cc=tzimmermann@suse.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