From: kernel test robot <lkp@intel.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>, robdclark@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, freedreno@lists.freedesktop.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
sean@poorly.run, Abaci Robot <abaci@linux.alibaba.com>,
quic_abhinavk@quicinc.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
dmitry.baryshkov@linaro.org, marijn.suijten@somainline.org
Subject: Re: [PATCH] drm/msm/a6xx: Remove some unused functions
Date: Wed, 18 Oct 2023 17:43:24 +0800 [thread overview]
Message-ID: <202310181742.3qvtq78e-lkp@intel.com> (raw)
In-Reply-To: <20231012024421.102832-1-jiapeng.chong@linux.alibaba.com>
Hi Jiapeng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20231016]
[cannot apply to drm-misc/drm-misc-next v6.6-rc6 v6.6-rc5 v6.6-rc4 linus/master v6.6-rc6]
[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/Jiapeng-Chong/drm-msm-a6xx-Remove-some-unused-functions/20231017-102229
base: next-20231016
patch link: https://lore.kernel.org/r/20231012024421.102832-1-jiapeng.chong%40linux.alibaba.com
patch subject: [PATCH] drm/msm/a6xx: Remove some unused functions
config: loongarch-randconfig-001-20231018 (https://download.01.org/0day-ci/archive/20231018/202310181742.3qvtq78e-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231018/202310181742.3qvtq78e-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/202310181742.3qvtq78e-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c:8:
>> drivers/gpu/drm/msm/adreno/a6xx_gpu_state.h:348:18: warning: 'a7xx_gbif_registers' defined but not used [-Wunused-const-variable=]
348 | static const u32 a7xx_gbif_registers[] = {
| ^~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/msm/adreno/a6xx_gpu_state.h:341:18: warning: 'a7xx_ahb_registers' defined but not used [-Wunused-const-variable=]
341 | static const u32 a7xx_ahb_registers[] = {
| ^~~~~~~~~~~~~~~~~~
vim +/a7xx_gbif_registers +348 drivers/gpu/drm/msm/adreno/a6xx_gpu_state.h
1707add815519d Jordan Crouse 2018-11-02 334
a5ab31767c7782 Sharat Masetty 2019-12-03 335 static const struct a6xx_registers a6xx_vbif_reglist =
a5ab31767c7782 Sharat Masetty 2019-12-03 336 REGS(a6xx_vbif_registers, 0, 0);
a5ab31767c7782 Sharat Masetty 2019-12-03 337
a5ab31767c7782 Sharat Masetty 2019-12-03 338 static const struct a6xx_registers a6xx_gbif_reglist =
a5ab31767c7782 Sharat Masetty 2019-12-03 339 REGS(a6xx_gbif_registers, 0, 0);
a5ab31767c7782 Sharat Masetty 2019-12-03 340
e997ae5f45caf7 Konrad Dybcio 2023-09-25 @341 static const u32 a7xx_ahb_registers[] = {
e997ae5f45caf7 Konrad Dybcio 2023-09-25 342 /* RBBM_STATUS */
e997ae5f45caf7 Konrad Dybcio 2023-09-25 343 0x210, 0x210,
e997ae5f45caf7 Konrad Dybcio 2023-09-25 344 /* RBBM_STATUS2-3 */
e997ae5f45caf7 Konrad Dybcio 2023-09-25 345 0x212, 0x213,
e997ae5f45caf7 Konrad Dybcio 2023-09-25 346 };
e997ae5f45caf7 Konrad Dybcio 2023-09-25 347
e997ae5f45caf7 Konrad Dybcio 2023-09-25 @348 static const u32 a7xx_gbif_registers[] = {
e997ae5f45caf7 Konrad Dybcio 2023-09-25 349 0x3c00, 0x3c0b,
e997ae5f45caf7 Konrad Dybcio 2023-09-25 350 0x3c40, 0x3c42,
e997ae5f45caf7 Konrad Dybcio 2023-09-25 351 0x3c45, 0x3c47,
e997ae5f45caf7 Konrad Dybcio 2023-09-25 352 0x3c49, 0x3c4a,
e997ae5f45caf7 Konrad Dybcio 2023-09-25 353 0x3cc0, 0x3cd1,
e997ae5f45caf7 Konrad Dybcio 2023-09-25 354 };
e997ae5f45caf7 Konrad Dybcio 2023-09-25 355
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-10-18 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 2:44 Jiapeng Chong
2023-10-18 9:43 ` 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=202310181742.3qvtq78e-lkp@intel.com \
--to=lkp@intel.com \
--cc=abaci@linux.alibaba.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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
all inboxes | Powered by JetHome®