From: kernel test robot <lkp@intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [krzk-github:b4/sm8750-display-dts-and-panel 87/88] drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.c:699:6: warning: variable 'val' set but not used
Date: Tue, 11 Feb 2025 01:40:34 +0800 [thread overview]
Message-ID: <202502110104.jEgR81mo-lkp@intel.com> (raw)
tree: https://github.com/krzk/linux b4/sm8750-display-dts-and-panel
head: 9c9642e37ccbac048317945fa497012c10aedc07
commit: a7fe47cf1a3d1699f276ae91354900afc05d69bd [87/88] DEBUG: testing ideas from Qcom
config: x86_64-buildonly-randconfig-005-20250210 (https://download.01.org/0day-ci/archive/20250211/202502110104.jEgR81mo-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250211/202502110104.jEgR81mo-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/202502110104.jEgR81mo-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.c:699:6: warning: variable 'val' set but not used [-Wunused-but-set-variable]
699 | u32 val = 0;
| ^
1 warning generated.
vim +/val +699 drivers/gpu/drm/msm/disp/dpu1/dpu_hw_ctl.c
e1a950eec25656e Abhinav Kumar 2022-04-26 694
2c266a634ad2814 Krzysztof Kozlowski 2025-01-13 695 static void dpu_hw_ctl_set_active_fetch_pipes(struct dpu_hw_ctl *ctx,
b3652e87c03c70d Krishna Manikandan 2021-04-06 696 unsigned long *fetch_active)
b3652e87c03c70d Krishna Manikandan 2021-04-06 697 {
b3652e87c03c70d Krishna Manikandan 2021-04-06 698 int i;
b3652e87c03c70d Krishna Manikandan 2021-04-06 @699 u32 val = 0;
b3652e87c03c70d Krishna Manikandan 2021-04-06 700
b3652e87c03c70d Krishna Manikandan 2021-04-06 701 if (fetch_active) {
b3652e87c03c70d Krishna Manikandan 2021-04-06 702 for (i = 0; i < SSPP_MAX; i++) {
b3652e87c03c70d Krishna Manikandan 2021-04-06 703 if (test_bit(i, fetch_active) &&
b3652e87c03c70d Krishna Manikandan 2021-04-06 704 fetch_tbl[i] != CTL_INVALID_BIT)
b3652e87c03c70d Krishna Manikandan 2021-04-06 705 val |= BIT(fetch_tbl[i]);
b3652e87c03c70d Krishna Manikandan 2021-04-06 706 }
b3652e87c03c70d Krishna Manikandan 2021-04-06 707 }
b3652e87c03c70d Krishna Manikandan 2021-04-06 708
a7fe47cf1a3d169 Krzysztof Kozlowski 2025-02-10 709 // DPU_REG_WRITE(&ctx->hw, CTL_FETCH_PIPE_ACTIVE, val);
b3652e87c03c70d Krishna Manikandan 2021-04-06 710 }
b3652e87c03c70d Krishna Manikandan 2021-04-06 711
:::::: The code at line 699 was first introduced by commit
:::::: b3652e87c03c70d8e6e04a17afa475f6855169d1 drm/msm/disp/dpu1: add support to program fetch active in ctl path
:::::: TO: Krishna Manikandan <mkrishn@codeaurora.org>
:::::: CC: Rob Clark <robdclark@chromium.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-10 17:40 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=202502110104.jEgR81mo-lkp@intel.com \
--to=lkp@intel.com \
--cc=krzk@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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