From: kernel test robot <lkp@intel.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 3/5] drm/gem: add functions to account GEM object memory usage
Date: Sat, 10 Sep 2022 15:14:44 +0800 [thread overview]
Message-ID: <202209101513.gIE9BRws-lkp@intel.com> (raw)
In-Reply-To: <20220909111640.3789791-4-l.stach@pengutronix.de>
Hi Lucas,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip linus/master v6.0-rc4]
[cannot apply to drm-misc/drm-misc-next next-20220909]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lucas-Stach/GEM-buffer-memory-tracking/20220909-191905
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-randconfig-a001 (https://download.01.org/0day-ci/archive/20220910/202209101513.gIE9BRws-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/612ea51433e7200c5da52be11b4b777133fbffdc
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Lucas-Stach/GEM-buffer-memory-tracking/20220909-191905
git checkout 612ea51433e7200c5da52be11b4b777133fbffdc
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_gem.c:1299:36: error: expected ';' after top-level asm block
EXPORT_SYMBOL(drm_gem_add_resident)
^
;
drivers/gpu/drm/drm_gem.c:1318:36: error: expected ';' after top-level asm block
EXPORT_SYMBOL(drm_gem_dec_resident)
^
;
2 errors generated.
vim +1299 drivers/gpu/drm/drm_gem.c
1282
1283 /**
1284 * drm_gem_add_resident - Account memory used by GEM object to the
1285 * task which called drm_gem_object_init(). Call when the pages are
1286 * made resident in system memory, i.e. pinned for GPU usage.
1287 *
1288 * @obj: GEM buffer object
1289 */
1290 void drm_gem_add_resident(struct drm_gem_object *obj)
1291 {
1292 if (!mmget_not_zero(obj->mm))
1293 return;
1294
1295 add_mm_counter(obj->mm, MM_DRIVERPAGES, obj->size / PAGE_SIZE);
1296
1297 mmput(obj->mm);
1298 }
> 1299 EXPORT_SYMBOL(drm_gem_add_resident)
1300
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-09-10 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220909111640.3789791-4-l.stach@pengutronix.de>
2022-09-10 7:04 ` [RFC PATCH 3/5] drm/gem: add functions to account GEM object memory usage kernel test robot
2022-09-10 7:14 ` 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=202209101513.gIE9BRws-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=l.stach@pengutronix.de \
--cc=llvm@lists.linux.dev \
/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