From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Rob Clark <robdclark@chromium.org>,
Abhinav Kumar <abhinavk@codeaurora.org>
Subject: [linux-next:master 3804/10007] drivers/gpu/drm/msm/dp/dp_display.c:1045:21: warning: variable 'drm' set but not used
Date: Wed, 16 Jun 2021 08:32:42 +0800 [thread overview]
Message-ID: <202106160834.PbZnBInf-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4291 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 19ae1f2bd9c091059f80646604ccef8a1e614f57
commit: 1c3b7ac1a71d4266d7243fe5f7cd530322c59583 [3804/10007] drm/msm: pass dump state as a function argument
config: arm64-randconfig-r015-20210615 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 64720f57bea6a6bf033feef4a5751ab9c0c3b401)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=1c3b7ac1a71d4266d7243fe5f7cd530322c59583
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 1c3b7ac1a71d4266d7243fe5f7cd530322c59583
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/gpu/drm/msm/dp/dp_display.c:506:19: warning: variable 'hpd' set but not used [-Wunused-but-set-variable]
struct dp_usbpd *hpd;
^
>> drivers/gpu/drm/msm/dp/dp_display.c:1045:21: warning: variable 'drm' set but not used [-Wunused-but-set-variable]
struct drm_device *drm;
^
2 warnings generated.
vim +/drm +1045 drivers/gpu/drm/msm/dp/dp_display.c
c943b4948b5848 Chandan Uddaraju 2020-08-27 1041
1c3b7ac1a71d42 Dmitry Baryshkov 2021-04-27 1042 void msm_dp_snapshot(struct msm_disp_state *disp_state, struct msm_dp *dp)
95e84adc2da78e Abhinav Kumar 2021-04-16 1043 {
95e84adc2da78e Abhinav Kumar 2021-04-16 1044 struct dp_display_private *dp_display;
95e84adc2da78e Abhinav Kumar 2021-04-16 @1045 struct drm_device *drm;
95e84adc2da78e Abhinav Kumar 2021-04-16 1046
95e84adc2da78e Abhinav Kumar 2021-04-16 1047 dp_display = container_of(dp, struct dp_display_private, dp_display);
95e84adc2da78e Abhinav Kumar 2021-04-16 1048 drm = dp->drm_dev;
95e84adc2da78e Abhinav Kumar 2021-04-16 1049
95e84adc2da78e Abhinav Kumar 2021-04-16 1050 /*
95e84adc2da78e Abhinav Kumar 2021-04-16 1051 * if we are reading registers we need the link clocks to be on
95e84adc2da78e Abhinav Kumar 2021-04-16 1052 * however till DP cable is connected this will not happen as we
95e84adc2da78e Abhinav Kumar 2021-04-16 1053 * do not know the resolution to power up with. Hence check the
95e84adc2da78e Abhinav Kumar 2021-04-16 1054 * power_on status before dumping DP registers to avoid crash due
95e84adc2da78e Abhinav Kumar 2021-04-16 1055 * to unclocked access
95e84adc2da78e Abhinav Kumar 2021-04-16 1056 */
95e84adc2da78e Abhinav Kumar 2021-04-16 1057 mutex_lock(&dp_display->event_mutex);
95e84adc2da78e Abhinav Kumar 2021-04-16 1058
95e84adc2da78e Abhinav Kumar 2021-04-16 1059 if (!dp->power_on) {
95e84adc2da78e Abhinav Kumar 2021-04-16 1060 mutex_unlock(&dp_display->event_mutex);
95e84adc2da78e Abhinav Kumar 2021-04-16 1061 return;
95e84adc2da78e Abhinav Kumar 2021-04-16 1062 }
95e84adc2da78e Abhinav Kumar 2021-04-16 1063
95e84adc2da78e Abhinav Kumar 2021-04-16 1064 dp_catalog_snapshot(dp_display->catalog, disp_state);
95e84adc2da78e Abhinav Kumar 2021-04-16 1065
95e84adc2da78e Abhinav Kumar 2021-04-16 1066 mutex_unlock(&dp_display->event_mutex);
95e84adc2da78e Abhinav Kumar 2021-04-16 1067 }
95e84adc2da78e Abhinav Kumar 2021-04-16 1068
:::::: The code at line 1045 was first introduced by commit
:::::: 95e84adc2da78e2c6db4dc59f1627c114c14e436 drm/msm/dp: add API to take DP register snapshot
:::::: TO: Abhinav Kumar <abhinavk@codeaurora.org>
:::::: CC: Rob Clark <robdclark@chromium.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33061 bytes --]
reply other threads:[~2021-06-16 0:33 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=202106160834.PbZnBInf-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhinavk@codeaurora.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=robdclark@chromium.org \
/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 NNTP newsgroup(s).