From: kernel test robot <lkp@intel.com>
To: Dipam Turkar <dipamt1729@gmail.com>, jani.nikula@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev,
Dipam Turkar <dipamt1729@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, daniel@ffwll.ch,
rodrigo.vivi@intel.com, airlied@gmail.com
Subject: Re: [Intel-gfx] [PATCH] Remove custom dumb_map_offset implementations in i915 driver
Date: Sat, 11 Nov 2023 02:20:00 +0800 [thread overview]
Message-ID: <202311110234.QjYxC2bv-lkp@intel.com> (raw)
In-Reply-To: <20231110105811.380646-1-dipamt1729@gmail.com>
Hi Dipam,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-tip/drm-tip]
url: https://github.com/intel-lab-lkp/linux/commits/Dipam-Turkar/Remove-custom-dumb_map_offset-implementations-in-i915-driver/20231110-185942
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link: https://lore.kernel.org/r/20231110105811.380646-1-dipamt1729%40gmail.com
patch subject: [Intel-gfx] [PATCH] Remove custom dumb_map_offset implementations in i915 driver
config: x86_64-randconfig-014-20231110 (https://download.01.org/0day-ci/archive/20231111/202311110234.QjYxC2bv-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231111/202311110234.QjYxC2bv-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311110234.QjYxC2bv-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/gem/i915_gem_mman.c: In function 'i915_gem_mmap_offset_ioctl':
drivers/gpu/drm/i915/gem/i915_gem_mman.c:673:16: error: implicit declaration of function '__assign_mmap_offset_handle' [-Werror=implicit-function-declaration]
673 | return __assign_mmap_offset_handle(file, args->handle, type, &args->offset);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/gem/i915_gem_mman.c: In function 'i915_gem_fb_mmap':
drivers/gpu/drm/i915/gem/i915_gem_mman.c:896:23: error: implicit declaration of function 'mmap_offset_attach' [-Werror=implicit-function-declaration]
896 | mmo = mmap_offset_attach(obj, mmap_type, NULL);
| ^~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/gem/i915_gem_mman.c:896:21: warning: assignment to 'struct i915_mmap_offset *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
896 | mmo = mmap_offset_attach(obj, mmap_type, NULL);
| ^
In file included from drivers/gpu/drm/i915/gem/i915_gem_mman.c:912:
drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c: In function 'assert_mmap_offset':
>> drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c:624:15: error: implicit declaration of function '__assign_mmap_offset'; did you mean 'assert_mmap_offset'? [-Werror=implicit-function-declaration]
624 | ret = __assign_mmap_offset(obj, default_mapping(i915), &offset, NULL);
| ^~~~~~~~~~~~~~~~~~~~
| assert_mmap_offset
cc1: some warnings being treated as errors
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for DRM_I915_DEBUG_GEM
Depends on [n]: HAS_IOMEM [=y] && DRM_I915 [=y] && EXPERT [=y] && DRM_I915_WERROR [=n]
Selected by [y]:
- DRM_I915_DEBUG [=y] && HAS_IOMEM [=y] && DRM_I915 [=y] && EXPERT [=y] && !COMPILE_TEST [=n]
vim +624 drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
450cede7f3804c Thomas Hellström 2021-08-31 611
b414fcd5be0b00 Chris Wilson 2019-05-28 612 static bool assert_mmap_offset(struct drm_i915_private *i915,
b414fcd5be0b00 Chris Wilson 2019-05-28 613 unsigned long size,
b414fcd5be0b00 Chris Wilson 2019-05-28 614 int expected)
b414fcd5be0b00 Chris Wilson 2019-05-28 615 {
b414fcd5be0b00 Chris Wilson 2019-05-28 616 struct drm_i915_gem_object *obj;
cf3e3e86d77970 Maarten Lankhorst 2021-06-10 617 u64 offset;
cf3e3e86d77970 Maarten Lankhorst 2021-06-10 618 int ret;
b414fcd5be0b00 Chris Wilson 2019-05-28 619
450cede7f3804c Thomas Hellström 2021-08-31 620 obj = create_sys_or_internal(i915, size);
b414fcd5be0b00 Chris Wilson 2019-05-28 621 if (IS_ERR(obj))
cf3e3e86d77970 Maarten Lankhorst 2021-06-10 622 return expected && expected == PTR_ERR(obj);
b414fcd5be0b00 Chris Wilson 2019-05-28 623
7961c5b60f23df Maarten Lankhorst 2021-07-14 @624 ret = __assign_mmap_offset(obj, default_mapping(i915), &offset, NULL);
b414fcd5be0b00 Chris Wilson 2019-05-28 625 i915_gem_object_put(obj);
b414fcd5be0b00 Chris Wilson 2019-05-28 626
cf3e3e86d77970 Maarten Lankhorst 2021-06-10 627 return ret == expected;
b414fcd5be0b00 Chris Wilson 2019-05-28 628 }
b414fcd5be0b00 Chris Wilson 2019-05-28 629
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-10 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 10:58 [PATCH] Remove custom dumb_map_offset implementations in i915 driver Dipam Turkar
2023-11-10 11:28 ` Tvrtko Ursulin
2023-11-10 16:52 ` [Intel-gfx] " kernel test robot
2023-11-10 18:20 ` kernel test robot [this message]
2023-11-10 18:37 ` kernel test robot
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=202311110234.QjYxC2bv-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dipamt1729@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@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