From: kernel test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev,
Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 09/20] drm/xe/guc_pc: s/pc_fini/pc_fini_hw/
Date: Sat, 11 May 2024 17:19:59 +0800 [thread overview]
Message-ID: <202405111645.xTy2cQ1s-lkp@intel.com> (raw)
In-Reply-To: <20240510181212.264622-31-matthew.auld@intel.com>
Hi Matthew,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on drm-misc/drm-misc-next next-20240510]
[cannot apply to linus/master v6.9-rc7]
[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/Matthew-Auld/drm-drm_managed-try-to-improve-the-drmm-DOC/20240511-061452
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20240510181212.264622-31-matthew.auld%40intel.com
patch subject: [PATCH 09/20] drm/xe/guc_pc: s/pc_fini/pc_fini_hw/
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20240511/202405111645.xTy2cQ1s-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240511/202405111645.xTy2cQ1s-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/202405111645.xTy2cQ1s-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/xe/xe_guc_pc.c:897: warning: Excess function parameter 'drm' description in 'xe_guc_pc_fini_hw'
vim +897 drivers/gpu/drm/xe/xe_guc_pc.c
dd08ebf6c3525a Matthew Brost 2023-03-30 890
bef52b5c7a1904 Rodrigo Vivi 2023-12-08 891 /**
d4543ae6de1c7e Matthew Auld 2024-05-10 892 * xe_guc_pc_fini_hw - Finalize GuC's Power Conservation component
8a4587ef9f9521 Michał Winiarski 2024-02-19 893 * @drm: DRM device
8a4587ef9f9521 Michał Winiarski 2024-02-19 894 * @arg: opaque pointer that should point to Xe_GuC_PC instance
bef52b5c7a1904 Rodrigo Vivi 2023-12-08 895 */
d4543ae6de1c7e Matthew Auld 2024-05-10 896 static void xe_guc_pc_fini_hw(void *arg)
dd08ebf6c3525a Matthew Brost 2023-03-30 @897 {
8a4587ef9f9521 Michał Winiarski 2024-02-19 898 struct xe_guc_pc *pc = arg;
975e4a3795d4f1 Vinay Belgaumkar 2023-11-17 899 struct xe_device *xe = pc_to_xe(pc);
975e4a3795d4f1 Vinay Belgaumkar 2023-11-17 900
975e4a3795d4f1 Vinay Belgaumkar 2023-11-17 901 if (xe->info.skip_guc_pc) {
975e4a3795d4f1 Vinay Belgaumkar 2023-11-17 902 xe_gt_idle_disable_c6(pc_to_gt(pc));
975e4a3795d4f1 Vinay Belgaumkar 2023-11-17 903 return;
975e4a3795d4f1 Vinay Belgaumkar 2023-11-17 904 }
975e4a3795d4f1 Vinay Belgaumkar 2023-11-17 905
fb74b205cdd263 Rodrigo Vivi 2024-04-23 906 if (xe_device_wedged(xe))
fb74b205cdd263 Rodrigo Vivi 2024-04-23 907 return;
fb74b205cdd263 Rodrigo Vivi 2024-04-23 908
649a125a88da64 Daniele Ceraolo Spurio 2024-03-18 909 XE_WARN_ON(xe_force_wake_get(gt_to_fw(pc_to_gt(pc)), XE_FORCEWAKE_ALL));
1737785ae5313e Riana Tauro 2023-07-17 910 XE_WARN_ON(xe_guc_pc_gucrc_disable(pc));
dd08ebf6c3525a Matthew Brost 2023-03-30 911 XE_WARN_ON(xe_guc_pc_stop(pc));
8a4587ef9f9521 Michał Winiarski 2024-02-19 912 xe_force_wake_put(gt_to_fw(pc_to_gt(pc)), XE_FORCEWAKE_ALL);
dd08ebf6c3525a Matthew Brost 2023-03-30 913 }
dd08ebf6c3525a Matthew Brost 2023-03-30 914
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-05-11 9:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240510181212.264622-31-matthew.auld@intel.com>]
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=202405111645.xTy2cQ1s-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).