From: kernel test robot <lkp@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
John Harrison <John.C.Harrison@intel.com>,
Alan Previn <alan.previn.teres.alexis@intel.com>
Subject: [drm-intel:drm-intel-gt-next 2/2] drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:352:20: error: unused function 'context_has_committed_requests'
Date: Fri, 19 Aug 2022 22:39:58 +0800 [thread overview]
Message-ID: <202208192254.jhkStQcS-lkp@intel.com> (raw)
drivers/gpu/drm/i915/gem/i915_gem_context.c
drivers/gpu/drm/i915/gt/intel_context.h
drivers/gpu/drm/i915/gt/intel_context_types.h
drivers/gpu/drm/i915/gt/uc/intel_guc.h
drivers/gpu/drm/i915/gt/uc/intel_guc_debugfs.c
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
drivers/gpu/drm/i915/i915_selftest.h
tree: git://anongit.freedesktop.org/drm-intel drm-intel-gt-next
head: 6a079903847cce1dd06345127d2a32f26d2cd9c6
commit: 6a079903847cce1dd06345127d2a32f26d2cd9c6 [2/2] drm/i915/guc: Add delay to disable scheduling after pin count goes to zero
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20220819/202208192254.jhkStQcS-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 0ac597f3cacf60479ffd36b03766fa7462dabd78)
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
git remote add drm-intel git://anongit.freedesktop.org/drm-intel
git fetch --no-tags drm-intel drm-intel-gt-next
git checkout 6a079903847cce1dd06345127d2a32f26d2cd9c6
# 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/i915/
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/i915/gt/uc/intel_guc_submission.c:352:20: error: unused function 'context_has_committed_requests' [-Werror,-Wunused-function]
static inline bool context_has_committed_requests(struct intel_context *ce)
^
1 error generated.
vim +/context_has_committed_requests +352 drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
62eaf0ae217d45 Matthew Brost 2021-07-26 351
5b116c17e6babc Matthew Brost 2021-09-09 @352 static inline bool context_has_committed_requests(struct intel_context *ce)
5b116c17e6babc Matthew Brost 2021-09-09 353 {
5b116c17e6babc Matthew Brost 2021-09-09 354 return !!ce->guc_state.number_committed_requests;
5b116c17e6babc Matthew Brost 2021-09-09 355 }
5b116c17e6babc Matthew Brost 2021-09-09 356
:::::: The code at line 352 was first introduced by commit
:::::: 5b116c17e6babc6de2e26714bc66228c74038b71 drm/i915/guc: Drop pin count check trick between sched_disable and re-pin
:::::: TO: Matthew Brost <matthew.brost@intel.com>
:::::: CC: John Harrison <John.C.Harrison@Intel.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-19 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202208192254.jhkStQcS-lkp@intel.com \
--to=lkp@intel.com \
--cc=John.C.Harrison@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
--cc=matthew.brost@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